Video Editing With Nodes

Skip the learning curve of professional editing software. Describe what you want — connect trim, color grade, and audio mix nodes to produce a finished cut —...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video-editing integration and mostly proportionate, but there are small metadata inconsistencies and clear privacy implications (user video files are uploaded to an external service) you should be comfortable with before installing.

Purpose & Capability

The name/description (node-based cloud video editing) align with required artifacts: a single service token (NEMO_TOKEN) and API calls to nemovideo.ai for session creation, uploads, renders, and status. Asking for a service token is expected for a cloud editor.

Instruction Scope

SKILL.md instructs the agent to create sessions, upload user video files, send SSE edits, poll render status, and return download URLs — all within the described purpose. It also instructs generating an anonymous token if NEMO_TOKEN is missing. Note: this will upload user media to an external API (mega-api-prod.nemovideo.ai), which is expected for cloud editing but has privacy implications. The file describes attribution headers and an 'auto-detect' platform value (which implies reading install path or environment), which is operationally reasonable but gives the agent extra system-sensing scope.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing will be written to disk by an installer; runtime behavior is purely API calls, so install risk is low.

Credentials

Only NEMO_TOKEN is declared as required, which is proportionate. SKILL.md also offers an anonymous-token flow (POST to /api/auth/anonymous-token) and instructs using that token as NEMO_TOKEN if none exists. The frontmatter in SKILL.md references a config path (~/.config/nemovideo/) where existing credentials might be found — the registry metadata shown earlier did not list config paths, so there is an inconsistency to clarify. Requiring a single service token is reasonable; do not provide unrelated credentials.

Persistence & Privilege

always:false (no forced always-on). The skill does not request system-wide privileges or control of other skills. Autonomous invocation is allowed by default but not excessive here.

Assessment

This skill appears to do what it says: it uploads the videos you drop into the chat to an external cloud service (mega-api-prod.nemovideo.ai) for node-based editing and returns downloadable outputs. Before installing: 1) be comfortable with uploading your video content to that external service and review its privacy/terms, 2) prefer supplying your own NEMO_TOKEN if you have an account rather than using the anonymous token flow, 3) confirm the endpoint hostname is legitimate and trusted, and 4) ask the skill author to resolve the small metadata mismatch (SKILL.md lists ~/.config/nemovideo/ but registry metadata omitted config paths) so you know whether the skill will read a local config file for stored tokens.

Getting Started

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

Try saying:

• "edit a 2-minute raw interview clip into a 1080p MP4"
• "connect trim, color grade, and audio mix nodes to produce a finished cut"
• "building non-destructive video edit pipelines using a visual node graph for video editors and motion designers"

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.

Video Editing With Nodes — Edit Videos Using Node Graphs

Drop your video clips in the chat and tell me what you need. I'll handle the node-based video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute raw interview clip, ask for connect trim, color grade, and audio mix nodes to produce a finished cut, 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 — keep your node graph shallow — fewer chained nodes means faster render times.

Matching Input to Actions

User prompts referencing video editing with nodes, 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	video-editing-with-nodes
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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "connect trim, color grade, and audio mix nodes to produce a finished cut" — 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 widest playback compatibility.

Common Workflows

Quick edit: Upload → "connect trim, color grade, and audio mix nodes to produce a finished cut" → 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.