Video Editor Opus
ReviewAudited by ClawScan on May 11, 2026.
Overview
This skill appears purpose-aligned for cloud video editing, but it will connect to NemoVideo, use or create a token, and upload selected media to a remote rendering service.
Use this skill if you are comfortable sending your selected footage to NemoVideo's cloud service. Keep NEMO_TOKEN private, review the provider's privacy/retention terms for sensitive videos, and expect the skill to start a remote session when invoked.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
You have less independent context about who maintains the skill or the remote service it uses.
The skill does not install local code, which lowers local execution risk, but the publisher/provenance and service homepage are not provided.
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill.
Use it only if you trust the NemoVideo API domain and are comfortable with the lack of listed homepage/source metadata.
After you invoke the skill, it may contact the remote API and perform video-editing workflow actions for the current session.
The agent is instructed to make provider API calls for session setup, upload, and export. These actions are central to the skill's purpose and are disclosed.
On first interaction, connect to the processing API before doing anything else... **Upload**: POST `/api/upload-video/nemo_agent/me/<sid>` ... **Export**: POST `/api/render/proxy/lambda`
Only provide files or editing/export requests you actually want processed by the remote service.
Anyone with the token could potentially use the associated NemoVideo credits or session access.
The skill uses a bearer token for the NemoVideo API. This is expected for the integration, and the instructions say not to print tokens.
If `NEMO_TOKEN` environment variable is already set, use it... **All requests** must include: `Authorization: Bearer <NEMO_TOKEN>`
Keep NEMO_TOKEN secret, avoid pasting it into chats or logs, and use a limited/throwaway token where possible.
Uploaded video files or URLs are shared with the NemoVideo service, not processed only on your machine.
The workflow sends user-provided footage to an external cloud service for processing. This is disclosed and purpose-aligned, but videos may contain private content.
Send me your raw video footage... All rendering happens server-side... **Upload**: POST `/api/upload-video/nemo_agent/me/<sid>`
Do not upload confidential, regulated, or third-party footage unless you are comfortable with the provider's privacy and retention practices.
A render job may continue remotely even if you close the tab before it finishes.
Remote render work may continue or become detached from the user interface if interrupted. This is a disclosed property of the cloud render workflow.
The session token carries render job IDs, so closing the tab before completion orphans the job.
Let exports complete when possible, and avoid starting render jobs you do not intend to finish.