Best Video Producer

Skip the learning curve of professional editing software. Describe what you want — cut the best moments, add transitions, and export a polished final video —...

Security Scan

The skill's requests and runtime instructions align with its stated purpose (cloud video production) and the only required secret (NEMO_TOKEN) is proportional to that function.

Purpose & Capability

Name/description indicate cloud-based video production and the SKILL.md instructs the agent to upload footage, create sessions, render, and download results from a single backend (mega-api-prod.nemovideo.ai). The declared primary credential (NEMO_TOKEN) and the documented endpoints are consistent with that purpose; there are no unrelated credentials, binaries, or install steps.

Instruction Scope

Instructions focus on uploading media, creating sessions, streaming SSE, polling render status, and handling errors—all expected. The skill instructs the agent to read its YAML frontmatter and to detect install-paths for attribution (checks like '~/.clawhub/' or '~/.cursor/skills/'), which implies verifying filesystem paths; this is reasonable for attribution but is the only runtime behavior that touches system state beyond handling provided media.

Install Mechanism

There is no install spec and no code files—this is an instruction-only skill. Nothing is written to disk or downloaded by the skill itself, which lowers install-time risk.

Credentials

Only one required environment variable (NEMO_TOKEN) is declared and used for Bearer auth—this matches the described cloud API usage. Note: NEMO_TOKEN is effectively a credential that can authorize uploads, rendering, and likely billing; the SKILL.md also contains logic to request an anonymous token from the backend if the env var is absent (creates a client UUID and exchanges it). That behavior is coherent but means a token may be created and used automatically if the user does not supply one.

Persistence & Privilege

always is false and the skill does not request persistent elevated privileges or to modify other skills. It creates per-session tokens and sessions with the backend as part of normal operation and does not claim to write to global agent settings.

Assessment

This skill appears to do what it says: it uploads your media to a cloud backend (mega-api-prod.nemovideo.ai), requests renders, and returns download URLs. Before installing: 1) Be aware that any files you upload will be sent to that external service—avoid uploading sensitive footage unless you trust its privacy policy; 2) NEMO_TOKEN grants access to the service and may be tied to billing/credits—provide a scoped account token if possible or expect the skill to request an anonymous token automatically; 3) confirm you trust the domain and review the service's terms and retention policy; 4) the skill will check local install paths for attribution metadata (read-only checks), which is normal but note it touches filesystem state. If you need higher assurance, request the skill's source or a privacy/billing statement from the publisher before use.

Getting Started

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

Try saying:

• "create my raw footage"
• "export 1080p MP4"
• "cut the best moments, add transitions,"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Best Video Producer — Produce and Export Finished Videos

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

Say you have a 2-minute raw interview recording and want to cut the best moments, add transitions, and export a polished final video — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source clips under 3 minutes produce the fastest and most focused results.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: best-video-producer
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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)

Common Workflows

Quick edit: Upload → "cut the best moments, add transitions, and export a polished final 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 "cut the best moments, add transitions, and export a polished final 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 all platforms and devices.