Free Video Downloader

Turn a YouTube video URL at 1080p into 1080p downloaded MP4 files just by typing what you need. Whether it's saving online videos to device for offline playb...

Security Scan

The skill's runtime instructions, requested env var, and declared config path are coherent with a cloud-based video download/rendering service — nothing requested appears unrelated to its stated purpose, but it contacts an external API and will handle tokens and uploads so review trust/privacy before using.

Purpose & Capability

The skill claims to perform cloud-based video downloads/renders and only asks for a NEMO_TOKEN and a nemovideo config path (~/.config/nemovideo/). Those requirements match the described external API endpoints (nemovideo.ai) and the stated cloud-render workflow.

Instruction Scope

Runtime instructions instruct the agent to contact nemovideo.ai, create/maintain a session_id, upload URLs or local files, and poll renders. They also direct the agent to detect install path (~/.clawhub, ~/.cursor/skills/) and to read/save session state. This is within the service's needs but does involve reading the agent filesystem for install-path detection and will transmit user-supplied files/URLs and the NEMO_TOKEN to the external API.

Install Mechanism

No install spec or third-party downloads are present (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install footprint.

Credentials

Only one environment credential (NEMO_TOKEN) is required and is the primary credential used for Bearer Authorization to the nemovideo API. The declared config path and token are proportionate to a cloud render/download service. The skill also provides an anonymous-token flow if NEMO_TOKEN isn't present, so it does not silently demand unrelated credentials.

Persistence & Privilege

The skill is not set to always:true and does not request system-wide persistence. It instructs storing session_id and state relevant to rendering jobs, which is expected behaviour for a session-driven remote service.

Assessment

This skill is internally coherent for a cloud-based video download/render service, but it will contact an external domain (mega-api-prod.nemovideo.ai), send your NEMO_TOKEN (or obtain an anonymous token), and may upload files or URLs you provide. Before installing: 1) Confirm you trust the nemovideo service and its privacy/terms (it will receive uploaded media and session metadata). 2) Do not reuse a high-privilege token as NEMO_TOKEN; prefer a scoped/limited token or use the anonymous-token flow if acceptable. 3) Be cautious about allowing any agent file-access: avoid pointing it at sensitive local files since uploads are supported. 4) If you need stronger assurance, request the skill's source or a reputable homepage and verify the API host and its TLS certificate and privacy policy. If you want a deeper analysis, provide the full SKILL.md or any additional metadata (owner contact, homepage) so I can reassess confidence.

Getting Started

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

Try saying:

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

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 Downloader — Download and Save Videos Locally

Drop your video URLs in the chat and tell me what you need. I'll handle the online video downloading on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a YouTube video URL at 1080p, ask for download this video as an MP4 file I can keep offline, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter videos download faster and are less likely to hit size limits.

Matching Input to Actions

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

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

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

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.

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.