Free Video Ai No Copyright

Turn a 60-second product demo clip into 1080p copyright-free videos just by typing what you need. Whether it's creating AI-edited videos with no copyright re...

Security Scan

The skill's network calls and token usage match its stated video-processing purpose, but there are small inconsistencies (metadata vs registry) and a need for filesystem and token persistence that you should review before installing or uploading sensitive videos.

Purpose & Capability

Name/description (AI video creation, export, royalty-free BGM) aligns with the runtime instructions: endpoints, upload, export, credits. The single required env var (NEMO_TOKEN) is appropriate. However, the SKILL.md frontmatter metadata declares a config path (~/.config/nemovideo/) whereas the registry Requirements block lists no required config paths — this mismatch is unexplained and worth verifying (it suggests the skill expects to read/write a local config directory).

Instruction Scope

The SKILL.md is prescriptive about network calls (session creation, SSE chat, upload, export polling) and token handling. All actions are within the claimed scope of cloud video rendering. The file/installation-path detection used to set X-Skill-Platform (checking ~/.clawhub/ or ~/.cursor/skills/) implies the agent may read filesystem locations to determine platform — reading those paths is not strictly necessary for core video processing and should be confirmed. Instructions to generate anonymous tokens and persist session_id are expected for this service but note that the skill will store/retain credentials/session identifiers.

Install Mechanism

No install spec and no code files — instruction-only skill. Lowest install risk; nothing will be written to disk by an installer. Runtime behavior will make outbound HTTPS requests to mega-api-prod.nemovideo.ai.

Credentials

Only NEMO_TOKEN is declared as required (and used as primaryEnv) which is proportionate. The SKILL.md also documents generating an anonymous token via the service if no NEMO_TOKEN exists, and saving session_id. The metadata's extra mention of a config path suggests the skill may read/write local config files to persist tokens — this should be validated because it increases the scope of local access.

Persistence & Privilege

always:false and user-invocable:true (normal). The skill instructs saving the session token/session_id for job management; that is reasonable for the service. There is no instruction to modify other skills or global agent settings.

What to consider before installing

This skill appears to do what it says (upload clips, talk to an external render API, return a download URL), but double-check the following before installing or using it with sensitive content: (1) Confirm whether the skill will read/write ~/.config/nemovideo/ or other local paths to persist tokens — if so, know where credentials will be stored and what protections exist. (2) Be aware that uploading videos sends your media to mega-api-prod.nemovideo.ai; do not upload private/sensitive footage unless you trust the service. (3) If you don't have or don't want to reuse a long-lived credential, use an anonymous/throwaway token (as described) or limit token scope. (4) Verify the service/domain reputation and privacy policy; ask the skill author to clarify the configPath usage and where session tokens are persisted.

Getting Started

Share your video clips and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "create my video clips"
• "export 1080p MP4"
• "generate a royalty-free background music track"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Free Video AI No Copyright — Create and Export Copyright-Free Videos

This tool takes your video clips and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second product demo clip and want to generate a royalty-free background music track and add it to my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: keeping clips under 2 minutes speeds up processing and avoids copyright match triggers on upload.

Matching Input to Actions

User prompts referencing free video ai no copyright, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...	Action	Skip SSE?
"export" / "导出" / "download" / "send me the video"	→ §3.5 Export	✅
"credits" / "积分" / "balance" / "余额"	→ §3.3 Credits	✅
"status" / "状态" / "show tracks"	→ §3.4 State	✅
"upload" / "上传" / user sends file	→ §3.2 Upload	✅
Everything else (generate, edit, add BGM…)	→ §3.1 SSE	❌

Cloud Render Pipeline Details

Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: free-video-ai-no-copyright
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Translating GUI Instructions

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
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a royalty-free background music track and add it to my video" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 for widest compatibility across YouTube, TikTok, and Instagram.

Common Workflows

Quick edit: Upload → "generate a royalty-free background music track and add it to my video" → Download MP4. Takes 30-60 seconds for a 30-second clip.

Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.

Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.