Video Downloader Online

Get downloaded MP4 files ready to post, without touching a single slider. Upload your video URL link (MP4, WebM, MOV, AVI, up to 500MB), say something like "...

Security Scan

The skill's stated purpose (remote video download/rendering via a Nemo backend) matches most of its runtime instructions and the single requested credential (NEMO_TOKEN), but there are small inconsistencies and privacy/behavior implications you should understand before installing.

Purpose & Capability

The name/description align with the instructions: the skill routes user URLs or uploaded files to a remote 'nemovideo' API that renders and returns downloadable media. Requesting a service token (NEMO_TOKEN) is expected. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch is unexplained and should be clarified.

Instruction Scope

SKILL.md instructs the agent to use NEMO_TOKEN or obtain an anonymous token (via POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token), create sessions, upload user files (multipart) or URLs, and poll render endpoints. Uploading local files and sending URLs to a third-party server is central to the skill but has privacy implications (user content is transmitted off-device). The instructions also require building attribution headers including an auto-detected X-Skill-Platform from an install path and matching frontmatter version; auto-detection may require reading agent/installation paths which isn’t fully specified. No instructions ask for unrelated system secrets, but the uploader behavior and path auto-detection are notable and should be explicit.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, which minimizes on-disk execution and supply-chain risk.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required and is used for API auth, which is proportionate. The skill will fall back to requesting an anonymous token from the service if NEMO_TOKEN is absent, which means it can operate without a user-supplied secret. The earlier-mentioned discrepancy about configPaths (present in SKILL.md metadata but not in registry fields) is a minor inconsistency to resolve.

Persistence & Privilege

always:false and normal autonomous invocation are in effect. The skill does not request elevated system persistence or access to other skills' configs. It will create remote sessions and jobs on the Nemo backend (which can be orphaned if the client disconnects), but it does not appear to modify local system-wide settings.

What to consider before installing

This skill appears to be what it says — a thin wrapper that sends user-provided video URLs or files to a remote Nemo service for rendering and returns a download link — but you should be cautious: (1) the skill uploads content to https://mega-api-prod.nemovideo.ai, so do not use it with sensitive/private/DRM-protected video unless you trust that service; (2) it will use NEMO_TOKEN if present or request an anonymous token automatically — prefer using a throwaway or limited-scope token if possible; (3) clarify the configPath/frontmatter mismatch with the publisher (why ~/.config/nemovideo/ is referenced and whether the agent will read local paths); (4) confirm the service's privacy/retention policy before uploading content; and (5) if you need stronger assurance, ask the publisher for the implementation code or an audited privacy statement before installing or granting the credential.

Getting Started

Got video URL link to work with? Send it over and tell me what you need — I'll take care of the online video downloading.

Try saying:

• "convert a YouTube video URL at 1080p into a 1080p MP4"
• "download this video as an MP4 file I can save to my device"
• "saving online videos to local device storage for students, content creators, marketers"

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.

Video Downloader Online — Download and Save Videos Locally

Send me your video URL link and describe the result you want. The online video downloading 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 save to my device", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter videos download faster and are less likely to hit size limits.

Matching Input to Actions

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

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

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

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

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.

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

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

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.

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)

Common Workflows

Quick edit: Upload → "download this video as an MP4 file I can save to my device" → 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 save to my device" — concrete instructions get better results.

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

MP4 with H.264 codec gives the best balance of quality and file size.