Best Video Download

Turn a YouTube video URL at 1080p into 1080p downloaded MP4 files just by typing what you need. Whether it's downloading online videos for offline use or qui...

Security Scan

The skill's declared purpose (cloud video download/render) mostly matches its runtime instructions, but there are inconsistencies and unanswered questions about where tokens/config are stored and who runs the backend, so proceed with caution.

Purpose & Capability

The skill claims to convert online video links to 1080p MP4 using a cloud backend and only requests a single credential (NEMO_TOKEN), which is appropriate for a cloud service. However, the skill's source/homepage are missing and the SKILL.md frontmatter references a config path (~/.config/nemovideo/) that is not listed in the registry metadata — an inconsistency that should be clarified.

Instruction Scope

Runtime instructions are explicit about contacting https://mega-api-prod.nemovideo.ai, creating sessions, uploading URLs/files, streaming SSE, and polling render status — all within the stated purpose. The instructions also describe generating an anonymous token if NEMO_TOKEN is absent and keeping a session_id. It is ambiguous whether the skill will persist that anonymous token or any session data to disk/config; SKILL.md warns not to 'expose tokens' but does not specify storage behavior.

Install Mechanism

Instruction-only skill with no install spec or code files. This is lowest-risk from an install perspective (nothing is downloaded or written by an installer).

Credentials

Only one environment variable (NEMO_TOKEN) is declared which fits the service. However, the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/), while the registry metadata lists no required config paths — this mismatch could imply the skill expects to read/write a local config directory (potentially containing other secrets). The skill's ability to mint an anonymous token via the backend is reasonable, but lack of clarity about whether tokens are persisted is a proportionality/privacy concern.

Persistence & Privilege

The skill is not marked always:true and does not request elevated or system-wide modifications. Autonomous invocation is allowed (the platform default) which increases runtime reach but is not itself a disqualifier. No instructions to modify other skills or global agent settings are present.

What to consider before installing

This skill mostly does what it says (uploads URLs/files to a cloud render service and returns MP4s), but there are a few things to check before installing or invoking it: 1) Verify the backend operator and privacy policy for https://mega-api-prod.nemovideo.ai (no homepage or source is provided). 2) Ask the author whether the anonymous NEMO_TOKEN or session_id will be stored under ~/.config/nemovideo/ (the registry metadata omits that path but SKILL.md references it). If tokens are persisted, confirm where and how they are protected and whether they can be revoked. 3) Avoid setting any sensitive or high-privilege tokens as NEMO_TOKEN — treat it as an API key that grants upload/render rights for your content. 4) Be aware you will upload video content (possibly private) to an external service — check copyright and privacy implications. 5) If you need stronger assurance, ask for the skill's source/homepage or prefer a skill backed by a known organization, or run interactions in a restricted/sandboxed environment. If you decide to proceed, monitor what the skill stores in ~/.config and limit the lifetime/permissions of any token it creates.

Getting Started

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

Try saying:

• "convert my online video links"
• "export 1080p MP4"
• "download this video in MP4 format"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Best Video Download — Download and Save Videos Locally

Send me your online video links and describe the result you want. The AI 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 in MP4 format at the highest available resolution", 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 easier to re-edit afterward.

Matching Input to Actions

User prompts referencing best 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

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

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

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

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

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

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)

Common Workflows

Quick edit: Upload → "download this video in MP4 format at the highest available resolution" → 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 in MP4 format at the highest available resolution" — 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.