Studio Video

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

Security Scan

The skill's runtime instructions mostly match a cloud video-processing service (it uploads user videos to an external API and uses a NEMO_TOKEN), but there are inconsistencies (metadata vs. registry fields) and some operational details that warrant caution before installing.

Purpose & Capability

The name/description (studio video editing) aligns with the skill's actions: uploading media, requesting renders, polling for download URLs, and requiring an API token (NEMO_TOKEN). That env var and the described endpoints are proportionate to a cloud video-editing service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) even though the registry metadata at the top said no required config paths — this mismatch is unexplained and should be clarified.

Instruction Scope

The instructions direct the agent to automatically create or use a bearer token, create sessions, upload user files, send SSE chat messages, and poll render endpoints on mega-api-prod.nemovideo.ai — all expected for a cloud render workflow. They also instruct not to display raw API responses or token values to the user (which may be a legitimate UX choice but also reduces visibility into what the skill stores/transmits). The skill will transmit user-provided video/audio/media to a third-party domain; users should understand their data will leave the device/agent.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That minimizes local code install risk.

Credentials

Only one credential is declared (NEMO_TOKEN) and the SKILL.md supports generating an anonymous temporary token if none is provided — this is proportionate for a third-party API. The unexplained frontmatter config path (~/.config/nemovideo/) is inconsistent with the top-level 'no required config paths' and raises the question of whether the skill expects to read/write local config files.

Persistence & Privilege

always:false and normal model invocation are used. The skill instructs to store a session_id and to persist/skip token creation based on NEMO_TOKEN, but it does not explicitly request permanent agent-wide privileges or to modify other skills. The place/form of any persistent storage (in-memory vs. disk vs. agent config) is unspecified — ask the author if persistent disk writes or agent config changes are performed.

What to consider before installing

This skill will upload your videos and audio to a third-party API (mega-api-prod.nemovideo.ai) and uses a bearer token (NEMO_TOKEN). Before installing or invoking it, consider: 1) Do you trust that external service with the media and potentially private content? 2) Confirm whether the skill will write tokens or session IDs to disk (the SKILL.md mentions a config path in its frontmatter but the registry listing omits it). 3) If you prefer not to provide a persistent credential, note the skill can create a temporary anonymous token (100 free credits for 7 days) — ask how/where that token and session_id are stored. 4) Because the source and homepage are unknown, prefer not to use this skill with sensitive or regulated content until you can verify the provider and inspect any persistent storage behavior. If you want to proceed, request the author to clarify the config path usage and where tokens/sessions are persisted, and to provide a homepage/source or privacy policy.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "clean up the audio, cut silences,"

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.

Studio Video — Edit Raw Footage Into Studio Quality

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

Say you have a 2-minute talking head recording from a webcam and want to clean up the audio, cut silences, and add an intro title card — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster and give you quicker iteration.

Matching Input to Actions

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

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

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

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.

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 → "clean up the audio, cut silences, and add an intro title card" → 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 "clean up the audio, cut silences, and add an intro title card" — 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.