Free Music Video Ai Generator
PassAudited by ClawScan on May 5, 2026.
Overview
The skill is coherent for cloud-based music-video generation, but it uploads user media to a third-party API and uses a service token, so users should review privacy and credit implications.
Before installing, be comfortable with a cloud service receiving your media and prompts. Use a dedicated NemoVideo token if available, avoid confidential or copyrighted material unless permitted, monitor credit/subscription limits despite the “free” branding, and ask the agent to confirm uploads and exports.
Findings (3)
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.
A token could be used to create sessions, check credits, upload files, and render jobs on the service.
The skill uses a bearer token to authorize all backend requests. That is expected for a provider integration, but it means the agent can act within the user’s NemoVideo session/credit boundary.
Every API call needs `Authorization: Bearer <NEMO_TOKEN>`
Use a dedicated token if possible, do not expose it in chat or logs, and monitor credit/subscription usage.
Audio, video, images, prompts, and generated output metadata may leave the local environment and be processed by the NemoVideo service.
The workflow sends user media or URLs to a third-party cloud backend. This is central to the skill’s purpose, but it is a meaningful data-sharing boundary.
**Upload**: POST `/api/upload-video/nemo_agent/me/<sid>` — file: multipart `-F "files=@/path"`, or URL: `{"urls":["<url>"],"source_type":"url"}`Only upload files you are comfortable sharing with that provider, and check the provider’s privacy, retention, and copyright terms before using sensitive or proprietary media.
If the backend returns unexpected GUI-style instructions, the agent may run service actions such as status checks or export steps without explaining each technical call.
Backend text can cause the agent to take follow-up service actions. The actions are constrained to the video-generation workflow, so this is a note rather than a concern.
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 ... 'Export' or '导出' → run the export workflow
Keep actions tied to the user’s request and ask for confirmation before uploads, exports, or any action that could consume credits or finalize output.