Free Youtube Free

Skip the learning curve of professional editing software. Describe what you want — download this YouTube video as an MP4 for free — and get downloaded MP4 fi...

Security Scan

The skill's declared purpose (download YouTube videos) matches its runtime instructions and required token, but there are metadata inconsistencies and some vague instructions about storing/hiding tokens and config paths that warrant caution before installing.

Purpose & Capability

The skill claims to download YouTube videos and its SKILL.md exclusively describes API calls to a single backend (mega-api-prod.nemovideo.ai) using a single credential (NEMO_TOKEN). Requesting a token to call that backend is proportionate to the stated purpose. However, the frontmatter references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained.

Instruction Scope

Instructions tell the agent to obtain an anonymous token if none is present, create and persist a session_id, upload local files via multipart (files=@/path) or by URL, and to suppress display of raw API responses or token values to the user. Uploading local file paths is expected for an upload flow, but the guidance to hide token values combined with unspecified persistence of tokens/session data and the referenced config path expands the agent's scope beyond a simple on-demand downloader and is potentially risky.

Install Mechanism

There is no install spec and no code files — this is an instruction-only skill, so nothing is written to disk by default. This is the lower-risk installation mode.

Credentials

The skill only declares one environment credential (NEMO_TOKEN), which is appropriate for an API-backed service. However, the SKILL.md frontmatter references a config directory (~/.config/nemovideo/) that the registry metadata did not declare—this inconsistency suggests the skill may read/write local config to persist tokens or sessions. The skill also instructs to generate and use anonymous tokens automatically (network calls to the backend), which is expected but worth noting because the agent will make outbound network requests and may persist session state.

Persistence & Privilege

The skill is not always-enabled and allows autonomous invocation (platform default). There is no install script, but instructions imply storing session_id (and possibly token) — unclear where and how. The agent may write to a per-skill config path (frontmatter) if implemented; that persistence is not explicitly declared in the registry metadata.

What to consider before installing

What to consider before installing: - Metadata mismatch: the SKILL.md frontmatter mentions ~/.config/nemovideo/ but the registry shows no required config paths — ask the publisher how/where session tokens are stored and whether the skill will write files to your home directory. - Token handling: the skill will either use your provided NEMO_TOKEN or automatically fetch an anonymous token by contacting mega-api-prod.nemovideo.ai. If you allow auto-generation, the agent will perform network calls and may persist session state; consider using an isolated environment or ephemeral credentials. - File uploads: the skill accepts local file paths for uploads (multipart files=@/path). Ensure the agent is only given paths you intend to upload; do not grant the skill broad filesystem access. - Privacy & legality: downloading YouTube content can violate service terms or copyright; be sure you have the right to download the content. - Trust & provenance: there is no homepage and source is unknown. If you need stronger assurance, request publisher contact info, a published source repo, or a reputable backend domain and verify who operates mega-api-prod.nemovideo.ai. - Minimum steps if you try it: run in a sandbox or VM, monitor network traffic to the nemovideo domain, do not provide other credentials, and check whether the skill creates files under ~/.config/nemovideo/. If the publisher can confirm where tokens/sessions are stored and provide a verifiable source or homepage, my confidence would rise; until then, proceed cautiously.

Getting Started

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

Try saying:

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

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free YouTube Free — Download YouTube Videos as MP4

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

Say you have a YouTube video URL pasted into the tool and want to download this YouTube video as an MP4 for free — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter videos download and process faster with no quality loss.

Matching Input to Actions

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

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

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

Header	Value
X-Skill-Source	free-youtube-free
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 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

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

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.

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 as an MP4 for free" → 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 YouTube video as an MP4 for free" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.