Free Video Download

Skip the learning curve of professional editing software. Describe what you want — download this video as an MP4 file I can keep offline — and get downloaded...

Security Scan

The skill mostly matches its stated purpose (downloading/converting videos via a backend) but has small metadata inconsistencies and asks the agent to access environment and filesystem context and to send user files to a third‑party API — things you should understand before installing.

Purpose & Capability

The skill's name/description (download/convert videos) aligns with the actions described: creating a session, uploading URLs/files, and requesting renders from a remote API. Requesting a NEMO_TOKEN as the primary credential is coherent for a hosted service.

Instruction Scope

SKILL.md explicitly instructs the agent to read NEMO_TOKEN from the environment (expected), generate an anonymous token if none exists (network call to obtain credentials), create sessions, upload local files (multipart @/path), and poll SSE endpoints. These behaviors are within the skill's purpose, but the instructions also tell the agent to detect an install path (~/.clawhub/, ~/.cursor/skills/) and include it in headers — reading install paths is extra context the skill asks for that is not strictly necessary for basic video upload/convert.

Install Mechanism

No install spec and no code files are present (instruction-only). This minimizes filesystem persistence risk; nothing is written to disk by an installer step.

Credentials

Only one credential (NEMO_TOKEN) is declared as required and is used in all API calls — proportionate for a hosted video service. However, SKILL.md frontmatter metadata also lists a config path (~/.config/nemovideo/) while the registry metadata reports 'Required config paths: none' — this mismatch is inconsistent and should be clarified. The skill also automatically fetches an anonymous token if none is present, which is convenient but means the agent will make network calls to obtain credentials on behalf of the user.

Persistence & Privilege

The skill does not request always:true and does not declare persistent system-wide changes. It requires a session for remote rendering but does not request elevated privileges or to modify other skills' config.

What to consider before installing

This skill appears to do what it says (upload a URL or local video and get a converted MP4 from a remote service) but before installing consider: (1) it will upload your files and send them to https://mega-api-prod.nemovideo.ai — don't send sensitive or private videos you wouldn't want stored/processed remotely; (2) it uses a NEMO_TOKEN if present, otherwise it will request an anonymous token for you (network call). Prefer using a short‑lived or limited token rather than a long‑lived secret; (3) there is a metadata inconsistency (declared config path in SKILL.md vs registry saying none) — ask the publisher to clarify why the skill needs ~/.config/nemovideo/ or to remove that requirement; (4) verify you trust the nemovideo.ai domain (check publisher/homepage and privacy policy), and avoid giving the skill other unrelated credentials. If you need greater assurance, request source code or a canonical homepage for the service and confirm where uploaded files are stored and how long they are retained.

Getting Started

Share your online video links and I'll get started on video downloading conversion. Or just tell me what you're thinking.

Try saying:

• "convert my online video links"
• "export 1080p MP4"
• "download this video as an MP4"

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.

Free Video Download — Download and Save Videos Locally

Send me your online video links and describe the result you want. The video downloading conversion runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a YouTube video URL at 1080p, type "download this video as an MP4 file I can keep offline", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter videos download and process faster with no queue wait.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-video-download, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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 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)

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 "download this video as an MP4 file I can keep offline" — 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.

Common Workflows

Quick edit: Upload → "download this video as an MP4 file I can keep offline" → Download MP4. Takes 20-40 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.