Best Video Downloader

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — download this YouTube video in MP4 format at the highest available resolut...

0· 104·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for linmillsd7/best-video-downloader.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Best Video Downloader" (linmillsd7/best-video-downloader) from ClawHub.
Skill page: https://clawhub.ai/linmillsd7/best-video-downloader
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install linmillsd7/best-video-downloader

ClawHub CLI

Package manager switcher

npx clawhub@latest install best-video-downloader
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill declares a video-download/editing purpose and only requests an API token (NEMO_TOKEN) and a config path (~/.config/nemovideo/) that are reasonable for contacting a remote rendering service. The listed endpoints and operations (upload, render, SSE) match the stated functionality.
Instruction Scope
SKILL.md instructs the agent to send user-provided URLs and uploaded media to mega-api-prod.nemovideo.ai, create sessions, stream SSE, and poll render status. That is expected for a cloud render pipeline, but it means user files and URLs will be transmitted externally. It also instructs reading the skill's frontmatter and detecting install path to populate attribution headers (requires local file/path inspection), which is within-skill scope but may expose limited environment info.
Install Mechanism
No install spec and no code files (instruction-only). This is the lowest-risk install model — nothing is written to disk by the skill itself beyond what the platform typically does.
Credentials
Only NEMO_TOKEN is required (primary credential) and a config path for the service is listed. These are proportionate to a third-party API client. The instructions do not request other unrelated secrets. Note: if NEMO_TOKEN is missing the skill will obtain an anonymous token from the service automatically.
Persistence & Privilege
always:false and normal invocation settings. There is no install-time persistence or modification of other skills; the skill does not request elevated platform privileges.
Assessment
This skill delegates downloading and processing to a third-party service (mega-api-prod.nemovideo.ai). Using it will transmit any URLs and uploaded media to that backend, and the skill will create or reuse an API token (NEMO_TOKEN) — if you don't supply one it will obtain an anonymous token automatically. Before installing, consider: (1) Do you trust nemovideo.ai with the media and URLs you provide? (2) Are there copyright/privacy concerns with uploading content to a cloud service? (3) The skill reads its own frontmatter and inspects install paths to set attribution headers (minor environment info may be sent). If you prefer not to send media externally, use a local downloader (e.g., yt-dlp) or only use this skill with non-sensitive material. If you do proceed, verify the token source and review the service's privacy/terms and any billing/credit implications.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

⬇️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk978y9t7bfv5gxh1ysp32p5pxn854nf4
104downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "convert my online video URLs"
  • "export 1080p MP4"
  • "download this YouTube video in 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.

Best Video Downloader — Download and Save Online Videos

This tool takes your online video URLs and runs video URL downloading through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a YouTube video URL at 1080p and want to download this YouTube video in MP4 format at the highest available resolution — the backend processes it in about 20-60 seconds and hands you a 1080p MP4.

Tip: shorter videos and lower resolutions download significantly faster.

Matching Input to Actions

User prompts referencing best video downloader, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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.

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

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

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

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

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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 saysYou 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)

Common Workflows

Quick edit: Upload → "download this YouTube video in MP4 format at the highest available resolution" → Download MP4. Takes 20-60 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 YouTube video in MP4 format at the highest available resolution" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across devices and platforms.

Comments

Loading comments...