Video Editing With Professional

Skip the learning curve of professional editing software. Describe what you want — cut the pauses, add color grading, and overlay background music — and get...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video-editing service, but it contacts an external API of unknown origin and will obtain/store short-lived tokens — review privacy and origin before installing.

Purpose & Capability

The skill is a cloud video-editing frontend. Requiring a single API token (NEMO_TOKEN) and an optional config path for a nemovideo config directory is consistent with that purpose. No unrelated binaries or credentials are requested.

Instruction Scope

SKILL.md limits activity to: authenticating (using an env var or obtaining an anonymous token), creating a session, uploading media, streaming edits via SSE, polling export status, and returning download URLs. It does not instruct reading arbitrary local files or unrelated credentials. Note: it will automatically request an anonymous token from the remote API if NEMO_TOKEN is not present and instructs storing session_id for subsequent calls.

Install Mechanism

Instruction-only skill with no install steps and no code files — lowest install risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as required, which is proportionate. Metadata lists a config path (~/.config/nemovideo/) — reasonable but not strictly necessary from the SKILL.md text. The skill will also generate and use anonymous tokens by contacting the remote API when NEMO_TOKEN is absent.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill asks to store session_id for requests but does not request system-wide changes or modify other skills. No elevated persistence is requested.

Assessment

This skill appears to do what it says: it uploads your videos to a cloud rendering service and returns edited output. Before installing, confirm you are comfortable sending your footage to the remote host (https://mega-api-prod.nemovideo.ai) — there is no homepage or vendor information in the registry metadata. Note the skill will either use an existing NEMO_TOKEN or obtain an anonymous token for you (100 free credits, valid 7 days) by POSTing to the provider; tokens and session IDs are used for subsequent calls. If you have sensitive video, do not use this skill until you verify the provider's identity, privacy policy, and data retention practices. Additional useful info that would increase confidence: an official homepage, privacy/security documentation, or a known vendor/registry entry for nemovideo.ai.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut the pauses, add color grading,"

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.

Video Editing with Professional — Edit Raw Footage to Pro Quality

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

Say you have a 3-minute unedited interview recording and want to cut the pauses, add color grading, and overlay background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: breaking long recordings into segments under 5 minutes speeds up processing significantly.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	video-editing-with-professional
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.

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add color grading, and overlay background music" — 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 file size.

Common Workflows

Quick edit: Upload → "cut the pauses, add color grading, and overlay background music" → 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.