Editor Youtube

Turn a 10-minute unedited YouTube vlog into 1080p YouTube-ready videos just by typing what you need. Whether it's editing and polishing videos for YouTube up...

Security Scan

The skill's instructions broadly match a cloud video-editing service, but metadata and runtime instructions disagree about required config/env and the skill directs uploading user videos and storing session tokens — the mismatches and token-handling guidance deserve scrutiny before installing.

Purpose & Capability

The skill's name and description (YouTube video editing) match the runtime actions (upload video, request cloud render, return download URL). Requesting a service token (NEMO_TOKEN) is expected. However, the registry metadata states no required config paths while the SKILL.md frontmatter lists ~/.config/nemovideo/ (inconsistency). Also the registry declares NEMO_TOKEN as required, but the SKILL.md provides an anonymous-token fallback path (it will create a token if none is present) — this mismatch should be clarified.

Instruction Scope

Instructions direct the agent to upload raw user video files to an external API (mega-api-prod.nemovideo.ai) and to persist a session_id for subsequent requests, which is coherent with the stated purpose but is sensitive (user media + session tokens leave the local environment). The instructions also tell the agent to 'don't display raw API responses or token values to the user', which implies the agent will handle/stash secrets internally — that behavior should be made explicit to the user. The SKILL.md also asks the agent to auto-detect platform from install path (may require reading agent environment/install path).

Install Mechanism

No install spec and no code files — instruction-only skill. This has lower installation risk because nothing will be downloaded or written by an installer step.

Credentials

Only one credential is declared (NEMO_TOKEN), which is proportional for a hosted editing service. But the registry claims it as required while SKILL.md describes generating an anonymous token if not present — a mismatch. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) even though the registry metadata lists none; it's unclear whether the skill will read or write that path.

Persistence & Privilege

always is false and there are no instructions to modify other skills or system-wide settings. The skill does instruct storing session_id and using tokens across requests (normal for web services) but does not request permanent elevated privileges.

What to consider before installing

This skill uploads your raw video files and stores a session token with a remote service. Before installing, confirm: (1) Are you comfortable sending your footage to https://mega-api-prod.nemovideo.ai? (2) Do you trust the service's privacy policy and retention practices? (3) Why does the registry declare NEMO_TOKEN as required while the skill can auto-generate an anonymous token, and why does the SKILL.md reference a local config path (~/.config/nemovideo/) that the registry omits? Ask the publisher to clarify these mismatches. If you must keep footage local or need auditability, do not install until you get explicit answers about token storage, where session data is kept, and how long uploads are retained.

Getting Started

Send me your raw video footage and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

• "edit a 10-minute unedited YouTube vlog into a 1080p MP4"
• "cut the pauses, add intro music, and export ready for YouTube upload"
• "editing and polishing videos for YouTube upload for YouTubers"

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.

YouTube Video Editor — Edit and Export YouTube Videos

Send me your raw video footage and describe the result you want. The AI video editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 10-minute unedited YouTube vlog, type "cut the pauses, add intro music, and export ready for YouTube upload", 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.

Matching Input to Actions

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

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

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

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.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add intro music, and export ready for YouTube upload" — 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 widest YouTube compatibility.

Common Workflows

Quick edit: Upload → "cut the pauses, add intro music, and export ready for YouTube upload" → 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.