Ai Free Video

Turn a 2-minute smartphone recording into 1080p polished MP4 videos just by typing what you need. Whether it's creating edited videos using free AI tools wit...

Security Scan

The skill's instructions mostly match a video-upload/rendering service and only request one credential (NEMO_TOKEN), but there are small metadata inconsistencies and clear privacy/network implications (uploads to an external API) that you should understand before installing.

Purpose & Capability

The name/description (remote AI video creation) align with the runtime instructions (create session, upload footage, render/export). The single declared credential (NEMO_TOKEN) is appropriate for an external API. However the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) while the registry metadata lists no required config paths — that mismatch is an incoherence (may be benign bookkeeping but worth noting).

Instruction Scope

Runtime instructions tell the agent to: read NEMO_TOKEN from env (or obtain an anonymous token via network call), create sessions, POST uploads (including multipart file uploads using local file paths), stream SSE responses, poll render status, and include attribution headers that disclose the skill name/version and detected platform. These actions are consistent with a cloud rendering service but mean the agent will transmit user video files and some agent metadata to a third party. There are no instructions to read unrelated system files, but the upload step requires access to local file paths (privacy risk).

Install Mechanism

This is an instruction-only skill with no install spec and no code to write to disk — lowest install risk.

Credentials

Only NEMO_TOKEN is required as the primary credential, which is proportional to calling the nemo API. The skill also specifies (in SKILL.md metadata) a config path (~/.config/nemovideo/) which wasn't surfaced in registry fields — inconsistent. The skill will acquire an anonymous token if NEMO_TOKEN is absent; this means network calls produce an ephemeral credential, which is expected but worth disclosing.

Persistence & Privilege

always is false and there's no install-time persistence or modification of other skill/system configs described. The skill will make network calls but does not request permanent platform-level privileges.

What to consider before installing

This skill appears to do what it says — upload your footage to a remote service for server-side rendering — but that implies sending your video files (which may be sensitive) and some agent metadata (skill/version/platform) to mega-api-prod.nemovideo.ai. Before installing: 1) confirm you trust that external service and its privacy policy, 2) decide whether you are comfortable providing NEMO_TOKEN or letting the skill obtain an anonymous token, 3) verify the configPath inconsistency (~/.config/nemovideo/ appears in SKILL.md but not in registry metadata) with the publisher if you need assurance, and 4) if you want to limit exposure, avoid uploading private footage or run the workflow on vetted/local tools instead. If you need higher confidence, ask the publisher/source of the skill (homepage/owner) for provenance and a link to official API docs or a GitHub repo.

Getting Started

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

Try saying:

• "create my raw video footage"
• "export 1080p MP4"
• "create a polished video from my"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Free Video — Create and Export Videos Free

Send me your raw video footage and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute smartphone recording, type "create a polished video from my footage without any paid tools", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing ai free video, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-free-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

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

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.

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

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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

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 "create a polished video from my footage without any paid tools" — 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 all platforms.

Common Workflows

Quick edit: Upload → "create a polished video from my footage without any paid tools" → Download MP4. Takes 1-2 minutes 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.