Video Writer

Turn a 2-minute raw product demo recording into 1080p scripted video content just by typing what you need. Whether it's generating written scripts and narrat...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video-processing service (it asks for a single service token and instructs uploading videos to that service), with a minor metadata inconsistency and the expected privacy implications of sending user video to an external API.

Purpose & Capability

The skill is described as a cloud video/script generation tool and only requests a single service token (NEMO_TOKEN) and access to a Nemovideo config path in its frontmatter — both are coherent with calling a remote API that performs rendering and script generation. No unrelated credentials or binaries are requested.

Instruction Scope

The SKILL.md directs the agent to obtain/use NEMO_TOKEN, create sessions, upload user video files (multipart uploads or by URL), stream SSE messages, and poll for render results at mega-api-prod.nemovideo.ai. This is expected for the described functionality, but it means user-supplied media and metadata will be sent to an external service; the instructions also tell the agent to generate a UUID for anonymous auth and to include attribution headers on every request. There are no instructions to read or exfiltrate unrelated local files or other environment variables.

Install Mechanism

No install spec or code is present (instruction-only). Nothing will be downloaded or written to disk by an installer step. This is lower risk and matches the listed metadata.

Credentials

The skill requires only NEMO_TOKEN as the primary credential, which is proportional to a remote API client. However, the YAML frontmatter in SKILL.md includes a configPaths requirement (~/.config/nemovideo/), while the registry metadata at the top of the evaluation listed 'Required config paths: none' — this mismatch is inconsistent and should be clarified. The skill also instructs detecting the agent install path to set an X-Skill-Platform header, which requires reading path information (minor scope).

Persistence & Privilege

always:false and user-invocable:true. The skill does not request persistent platform privileges or to modify other skills' configurations. It is an instruction-only skill that relies on runtime API calls.

Assessment

This skill appears to do what it says: it sends user video clips and requests rendering/script generation from a Nemovideo cloud API and needs a NEMO_TOKEN to authenticate. Before installing/using it: (1) Confirm you trust mega-api-prod.nemovideo.ai — your video files and any metadata you send will be uploaded to that external service. (2) If you don't already have a NEMO_TOKEN, the skill will generate an anonymous token (100 credits, 7-day expiry) by posting a UUID to the service — be aware this creates a server-side account tied to that identifier. (3) Ask the publisher to clarify the configPaths discrepancy in the SKILL.md frontmatter (~/.config/nemovideo/) vs the registry listing (none). (4) Do not use this skill with sensitive or private footage unless you have verified the provider's privacy/retention policy. If you want higher assurance, request a published homepage/privacy policy or vendor identity before providing tokens or private media.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "generate a 2-minute raw product demo recording into a 1080p MP4"
• "write a compelling voiceover script based on my video content"
• "generating written scripts and narration from raw video footage for content creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Writer — Generate Scripts from Video

Drop your video clips in the chat and tell me what you need. I'll handle the AI script writing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute raw product demo recording, ask for write a compelling voiceover script based on my video content, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 3 minutes produce tighter, more focused scripts.

Matching Input to Actions

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

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

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

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

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 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 → "write a compelling voiceover script based on my video content" → Download MP4. Takes 30-60 seconds 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 "write a compelling voiceover script based on my video content" — 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.