Free Youtube Best

create YouTube video links into optimized YouTube videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers use it for creating pol...

Security Scan

The skill's instructions, requested credential (NEMO_TOKEN), and network calls align with a cloud video-processing service; nothing obviously unrelated is requested, but there are a few small inconsistencies you should verify before installing.

Purpose & Capability

Name/description match the runtime instructions: it uploads or points to video files, opens a session, streams edits, and requests renders from a remote API. The single required credential (NEMO_TOKEN) is appropriate for an external video processing service.

Instruction Scope

Instructions consistently describe creating sessions, uploading files or URLs, reading SSE streams, polling render status, and returning download URLs — all expected. Two small items to note: the SKILL.md metadata references a config path (~/.config/nemovideo/) and the agent is told to detect an install path to populate an attribution header, which implies the skill may inspect local install paths; the current instructions do not otherwise ask the agent to read unrelated files or other secrets.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is downloaded or written during installation — lowest-risk install model.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv) which is proportional for access to the remote API. However, SKILL.md metadata includes a configPaths entry (~/.config/nemovideo/) while the registry metadata earlier listed none — this mismatch should be clarified because configPaths implies the skill may access local configuration files.

Persistence & Privilege

The skill is not always-enabled and requests no unusual persistent privileges. It will operate over the network and can be invoked autonomously (the platform default), which increases blast radius but is expected for such a skill.

Assessment

This skill appears to be a front-end for a cloud video-rendering service and only needs an API token (NEMO_TOKEN). Before installing: 1) Confirm the NEMO_TOKEN provider is trustworthy and that you understand how to revoke the token (avoid using long-lived tokens for general use). 2) Don't upload sensitive or private content — uploads go to a third-party domain (mega-api-prod.nemovideo.ai). 3) Ask the publisher to clarify the metadata mismatch (SKILL.md lists ~/.config/nemovideo/ while registry metadata lists no config paths) and whether the skill will read local install/config files to populate attribution headers. 4) Test first with non-sensitive sample videos to ensure behavior matches expectations. If any of those answers are unsatisfactory, do not install or supply real credentials.

Getting Started

Send me your YouTube video links and I'll handle the AI video optimization. Or just describe what you're after.

Try saying:

• "create a 10-minute YouTube tutorial video into a 1080p MP4"
• "trim the video, add captions, and optimize it for YouTube engagement"
• "creating polished YouTube videos for free for YouTubers"

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.

Free YouTube Best — Create and Export YouTube Videos

Send me your YouTube video links and describe the result you want. The AI video optimization runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 10-minute YouTube tutorial video, type "trim the video, add captions, and optimize it for YouTube engagement", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 5 minutes process significantly faster and use fewer credits.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-youtube-best, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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.

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)

Common Workflows

Quick edit: Upload → "trim the video, add captions, and optimize it for YouTube engagement" → Download MP4. Takes 1-2 minutes 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 "trim the video, add captions, and optimize it for YouTube engagement" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best YouTube upload compatibility.