Make Video

Skip the learning curve of professional editing software. Describe what you want — trim the footage, add background music, and export as a shareable video —...

Security Scan

The skill's declared purpose (remote AI video editing) matches its runtime instructions (upload footage, create session, call a nemo video API); there are a few minor metadata inconsistencies and privacy considerations to review before use.

Purpose & Capability

The skill claims to create and export videos and its instructions call a remote video-processing API and upload user media — this is consistent. Minor inconsistency: the top-level registry metadata lists no required config paths, but the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). That mismatch is likely an authoring oversight.

Instruction Scope

SKILL.md explicitly instructs the agent to obtain/verify a session token, create a session, upload files (multipart or by URL), stream SSE messages, poll render status, and return download URLs. All actions are within the stated video-editing purpose. Note: these instructions send user media and session tokens to a third-party API (mega-api-prod.nemovideo.ai)—expected for a cloud render service but important privacy behavior to surface to users.

Install Mechanism

This is an instruction-only skill with no install spec and no code files; that is the lowest install risk and matches the declared metadata.

Credentials

The only required credential is NEMO_TOKEN, which is appropriate for a single third-party video service. The SKILL.md also instructs the agent to auto-request an anonymous token if NEMO_TOKEN is not present — acceptable but a small inconsistency with the notion of a pre-provided primaryEnv. No unrelated credentials are requested.

Persistence & Privilege

always is false and the skill does not request system-wide changes. It stores a session_id for API calls (expected). The agent-autonomy default is allowed and not, by itself, a concern.

Assessment

This skill appears to do what it says: it uploads your video files to a remote nemo video API, creates sessions, streams progress, and returns download links. Before installing: (1) confirm you trust the service domain (mega-api-prod.nemovideo.ai) and review its privacy policy because your raw footage will be uploaded; (2) be aware the skill can auto-generate an anonymous token if you don't provide NEMO_TOKEN (so it can operate without preconfigured credentials); (3) the SKILL.md and registry metadata disagree about a config path (~/.config/nemovideo/) — minor but ask the publisher to clarify; (4) if your footage contains sensitive data, avoid using third‑party cloud renderers or restrict use to vetted accounts. If you need stronger assurance, ask the publisher for a homepage, privacy/security documentation, or the service's official SDK/docs before enabling the skill.

Getting Started

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

Try saying:

• "create a 2-minute phone recording of a product demo into a 1080p MP4"
• "trim the footage, add background music, and export as a shareable video"
• "turning raw footage into a finished, shareable video for content creators"

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.

Make Video — Create and Export Finished Videos

Send me your raw footage and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute phone recording of a product demo, type "trim the footage, add background music, and export as a shareable video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing make video, 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.

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

Header	Value
X-Skill-Source	make-video
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.

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.

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.

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 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)

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 → "trim the footage, add background music, and export as a shareable video" → 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 the footage, add background music, and export as a shareable video" — 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 platforms and devices.