Video Editing For Ai

edit raw video footage into AI-edited clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it for usin...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video-editing integration that uses a single API token; no disproportionate credentials, installs, or privileged behavior are requested.

Purpose & Capability

Name/description (cloud AI video editing) align with the single required credential (NEMO_TOKEN) and the documented API endpoints (upload, render, export). Requiring an API token for a cloud service is expected.

Instruction Scope

SKILL.md focuses on connecting to the remote nemovideo API, uploading media, controlling an SSE/chat stream, and polling render state — all within the stated purpose. It does instruct the agent to create an anonymous token if none is present and to 'auto-detect' platform from an install path; that implies the agent may inspect its environment/install path, but the instructions do not ask for unrelated files or secrets.

Install Mechanism

There is no install spec and no code files; the skill is instruction-only so nothing is written to disk by an installer. This is the lowest-risk install posture.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which is proportionate for a cloud video-editing service. Metadata also lists a configPath (~/.config/nemovideo/) that is not referenced in the runtime instructions — this is likely optional but worth confirming since it suggests possible local config access.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill does not request system-wide changes or other skills' credentials.

Assessment

This skill appears to do what it says: it uploads your videos to nemovideo.ai and uses a NEMO_TOKEN to authenticate. Before installing, consider: (1) You will be sending raw media to an external cloud service — only upload content you are comfortable sharing. (2) If you don't provide NEMO_TOKEN, the skill will request an anonymous token from the provider (7-day, limited credits). (3) Metadata mentions a local config path (~/.config/nemovideo/) which could be used to read a saved token — confirm whether you want the skill to access local config. (4) There is no local installer or code, so risk is primarily data exposure to the remote API; verify the provider and privacy/terms if that matters. If you need tighter control, supply your own NEMO_TOKEN and avoid uploading sensitive videos.

Getting Started

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

Try saying:

• "edit a 2-minute screen recording or phone clip into a 1080p MP4"
• "cut the pauses, add b-roll transitions, and export a clean 60-second version"
• "using AI to automatically cut, trim, and polish raw video footage for content creators and marketers"

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 for AI — Edit and Export AI-Ready Videos

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

Say you have a 2-minute screen recording or phone clip and want to cut the pauses, add b-roll transitions, and export a clean 60-second version — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 90 seconds process significantly faster and give the AI more precise results.

Matching Input to Actions

User prompts referencing video editing for ai, 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-for-ai
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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 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

Common Workflows

Quick edit: Upload → "cut the pauses, add b-roll transitions, and export a clean 60-second version" → 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 pauses, add b-roll transitions, and export a clean 60-second version" — 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 compatibility across platforms.