Youtube Video Editing With

Cloud-based youtube-video-editing-with tool that handles editing raw footage into upload-ready YouTube videos. Upload MP4, MOV, AVI, WebM files (up to 500MB)...

Security Scan

The skill's runtime instructions mostly match a cloud video-editing service, but there are metadata/instruction mismatches and clear privacy/exfiltration implications (automatic token acquisition + uploads to an external API) that you should understand before installing.

Purpose & Capability

The name/description (cloud YouTube video editing) lines up with the endpoints and SSE-based render pipeline described in SKILL.md. Requiring a service token (NEMO_TOKEN) and a nemovideo config path is consistent with a hosted editing backend. However the registry header given to you earlier said 'Required config paths: none' while SKILL.md metadata lists '~/.config/nemovideo/' — this is an inconsistency in the skill metadata.

Instruction Scope

SKILL.md explicitly instructs the agent to upload user media to https://mega-api-prod.nemovideo.ai and to automatically obtain an anonymous token if NEMO_TOKEN isn't present. That behavior is coherent for a cloud editing service, but it means user video files (possibly sensitive) will be transmitted to an external service. Also the skill instructs the agent to 'connect automatically when a user first opens the skill' and to 'store the returned session_id' — it's not explicit where/how persistent storage is performed. The instructions do not request unrelated system files or other credentials, which is good.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That minimizes on-disk code risk; nothing is downloaded or installed by the skill itself.

Credentials

The skill declares a single primary env var (NEMO_TOKEN) which is appropriate for a hosted service. But the registry summary you were shown earlier listed 'Required config paths: none' while the SKILL.md metadata requests '~/.config/nemovideo/'. More importantly, the SKILL.md will auto-generate and use an anonymous token if NEMO_TOKEN is not set — so marking NEMO_TOKEN as 'required' in registry metadata is inconsistent. Automatic token creation means the skill can obtain credentials and use them without the user supplying secrets.

Persistence & Privilege

always:false (default) and the skill does not request system-wide privileges. However it instructs the agent to 'connect automatically' on first use and to 'store' session tokens; you should confirm whether stored tokens are persisted to the declared config path and for how long (SKILL.md says anonymous token valid 7 days). Autonomous invocation is allowed (normal) and combined with automatic token acquisition this increases the chance the skill will upload data without an additional explicit user action.

What to consider before installing

This skill appears to implement a cloud video-editing workflow and will upload user media to an external service (mega-api-prod.nemovideo.ai). Before installing: (1) Decide whether you trust that external provider with your videos (sensitive footage will leave your device). (2) Note the skill will either use NEMO_TOKEN from env or automatically obtain an anonymous token and store session state — ask where tokens/session IDs are persisted (the SKILL.md mentions '~/.config/nemovideo/'). (3) Verify the registry metadata vs SKILL.md mismatch (config path vs 'none' and NEMO_TOKEN labeled required but auto-obtained) — ask the publisher to clarify. (4) If you prefer control, set your own NEMO_TOKEN and confirm the agent will not create/retain tokens automatically. If any of these points are unacceptable or unclear, do not install or invoke the skill.

Getting Started

Share your raw video footage and I'll get started on AI video editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut the dead air, add transitions,"

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 Editing With AI — Edit and Export YouTube-Ready Videos

This tool takes your raw video footage and runs AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 10-minute unedited vlog recording and want to cut the dead air, add transitions, and put my channel intro at the start — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: splitting your video into shorter segments before uploading speeds up processing significantly.

Matching Input to Actions

User prompts referencing youtube video editing with, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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-video-editing-with, 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).

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

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)

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

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.

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

Common Workflows

Quick edit: Upload → "cut the dead air, add transitions, and put my channel intro at the start" → 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 "cut the dead air, add transitions, and put my channel intro at the start" — 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 balance of quality and YouTube upload compatibility.