Video A2e
PassAudited by ClawScan on May 3, 2026.
Overview
The skill appears to do what it advertises—send user-provided media to a NemoVideo cloud API for rendering—but users should notice the external upload, token use, and limited provenance.
Before installing, be sure you are comfortable sending media files and editing prompts to NemoVideo, using a NEMO_TOKEN or anonymous token, and potentially consuming credits for render/export jobs. Avoid uploading sensitive content unless you trust the provider.
Findings (4)
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.
Audio, video, image files, and related prompts may be processed outside the local environment.
The skill discloses that user messages and uploaded media are sent to an external cloud provider for processing.
Base URL: `https://mega-api-prod.nemovideo.ai` ... `/run_sse` | POST | Send a user message ... `/api/upload-video/nemo_agent/me/<sid>` | POST | Upload a file
Only upload media you are comfortable sending to NemoVideo, and avoid confidential or regulated content unless you trust the provider and its terms.
The skill may use your NemoVideo account token or anonymous credits to create sessions and run rendering jobs.
The skill uses or creates a bearer token for the NemoVideo service, which is expected for this integration but still grants service access and credits.
If `NEMO_TOKEN` is in the environment, use it directly ... Otherwise, acquire a free starter token ... Every API call needs `Authorization: Bearer <NEMO_TOKEN>`
Use a dedicated token where possible, monitor credit usage, and revoke or rotate the token if you stop using the skill.
The remote workflow may perform edits or rendering steps based on backend responses, so users should ensure important actions match their request.
The skill allows backend-provided responses to trigger additional API actions. This is purpose-aligned for a remote editing service, but it is operational control beyond simple text output.
The backend responds as if there's a visual interface. Map its instructions to API calls: - "click" or "点击" → execute the action via the relevant endpoint
Keep high-impact actions such as uploads, exports, or credit-consuming renders tied to explicit user requests or confirmations.
Users have less information to verify who maintains the skill or the service integration.
The registry metadata does not provide a verifiable source or homepage for the skill, limiting independent provenance checks.
Source: unknown; Homepage: none
Install only if you are comfortable with the publisher and the NemoVideo API endpoint documented in the skill.