Youtube Ai Video Editor

Skip the learning curve of professional editing software. Describe what you want — trim dead air, add transitions, and generate auto-captions in English — an...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based AI video editor: it needs a single API token (NEMO_TOKEN), uploads user media to a remote rendering API, and manages per-session tokens — nothing requested appears disproportionate, though there are small metadata inconsistencies you should note before use.

Purpose & Capability

The skill's name/description (YouTube AI video editing) matches its actions: obtaining a token, creating a session, uploading video files, streaming SSE edits, and requesting renders from a cloud API. Requiring an API token (NEMO_TOKEN) is appropriate. The only mismatch is that the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata provided to the scanner listed no config paths — this is a metadata inconsistency but not itself indicative of malicious behavior.

Instruction Scope

Runtime instructions are narrowly scoped to: (1) use or create a NEMO_TOKEN, (2) create a session, (3) upload user media, (4) process SSE responses and start renders, and (5) return download URLs. The skill instructs saving session_id and not printing tokens. It does instruct deriving X-Skill-Platform from the agent's install path (which can reveal which folder the skill was installed into), and it sends files and metadata to https://mega-api-prod.nemovideo.ai — both expected for a cloud editor but worth being aware of because user media and session identifiers are transmitted to an external service.

Install Mechanism

There is no install spec and no code files — this is instruction-only. That is the lowest-risk install mechanism: nothing is downloaded or written to disk by an installer step beyond what the agent normally does at runtime.

Credentials

The skill requests only one environment credential: NEMO_TOKEN (declared as primaryEnv). SKILL.md also describes a flow to obtain an anonymous token if none is set, which is coherent. The earlier-noted discrepancy where SKILL.md frontmatter lists a config path (~/ .config/nemovideo/) but the registry metadata did not declare configPaths is an inconsistency to verify. There are no unrelated secrets requested.

Persistence & Privilege

The skill is not always-enabled and does not request special privileges. It instructs saving a session_id for job tracking, which is normal behavior for session-based cloud services. It does not modify other skills or system-wide settings.

Assessment

This skill appears to do what it says: it uploads your video files to a third-party cloud API (mega-api-prod.nemovideo.ai) and uses a single token (NEMO_TOKEN) to authenticate. Before installing or using it: (1) verify the external domain and service are legitimate and acceptable for your content (check privacy, retention, and terms of service); (2) be aware that uploading any sensitive or private footage will transmit it off your device; (3) confirm whether the registry metadata and the SKILL.md frontmatter agree (SKILL.md mentions ~/.config/nemovideo/ while the registry did not) — small metadata mismatches should be resolved; (4) note the skill will derive an X-Skill-Platform header from install path (may reveal installation folder) — if that concerns you, ask the publisher to remove or clarify that behavior; and (5) if you lack a NEMO_TOKEN, the skill can obtain an anonymous short-lived token — understand what data and usage those anonymous tokens allow and how long files are kept. Absence of scanner findings is not proof of safety: this is an instruction-only skill that will transmit your data to an external service, so review the service before uploading sensitive content.

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

• "edit a 10-minute unedited YouTube vlog into a 1080p MP4"
• "trim dead air, add transitions, and generate auto-captions in English"
• "editing and polishing YouTube videos with AI for YouTubers"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

YouTube AI Video Editor — Edit and Export YouTube Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 10-minute unedited YouTube vlog, ask for trim dead air, add transitions, and generate auto-captions in English, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 5 minutes process significantly faster.

Matching Input to Actions

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

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process 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 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 dead air, add transitions, and generate auto-captions in English" → 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 dead air, add transitions, and generate auto-captions in English" — 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 across YouTube and all devices.