Program Video

edit raw video footage into programmed video files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and educators use it f...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud video-processing service: it needs one service token, uploads files, and talks to the nemo video API; nothing in the instructions tries to access unrelated credentials or system files, but there's a small metadata inconsistency to be aware of.

Purpose & Capability

Skill name/description (AI cloud video editing) match the declared runtime behavior: it uploads video, creates render jobs, polls for results, and requires a NEMO_TOKEN for the backend API. The required network endpoints and headers align with a video rendering backend.

Instruction Scope

SKILL.md instructs only session creation, uploading video files (multipart or URL), sending edit messages via SSE, querying status/credits, and exporting results. It does not instruct reading arbitrary system files or unrelated environment variables. All actions described are within the domain of remote video processing.

Install Mechanism

This is instruction-only with no install spec or code files, so nothing is written to disk or downloaded by an installer — the lowest-risk install profile.

Credentials

The only required credential is NEMO_TOKEN (primaryEnv), which is proportional for a remote service. However, the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch should be resolved. The skill will also create an anonymous token via network request if no NEMO_TOKEN is present (network activity is expected but worth noting).

Persistence & Privilege

always is false; the skill does not request permanent agent presence or modify other skills' configs. It performs remote API calls and manages session tokens only for its own operations.

Assessment

This skill behaves like a cloud video-editing client: it will upload your video files to mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN (or will obtain a short-lived anonymous token). Before installing, consider: (1) privacy — your footage is sent off-site (avoid sensitive content unless you trust the service); (2) billing/credits — anonymous tokens have limits and some endpoints may require paid tiers; (3) verify the service domain and terms (the skill has no homepage or known owner listed); (4) note the small metadata inconsistency: SKILL.md mentions a config path (~/.config/nemovideo/) even though the registry shows none — clarify whether the skill will read or write that folder. If those items are acceptable, the skill's requested access appears proportionate to its purpose.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut out pauses, add chapter markers,"

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.

Program Video — Sequence and Export Edited Videos

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

Say you have a 2-minute screen recording of a software demo and want to cut out pauses, add chapter markers, and overlay a title sequence — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: breaking your footage into shorter segments before uploading speeds up processing significantly.

Matching Input to Actions

User prompts referencing program 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.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Header	Value
X-Skill-Source	program-video
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)

Common Workflows

Quick edit: Upload → "cut out pauses, add chapter markers, and overlay a title sequence" → 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 out pauses, add chapter markers, and overlay a title sequence" — 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.