Video Script

generate text or brief into ready-to-film scripts with this skill. Works with TXT, DOCX, PDF, MP4 files up to 200MB. YouTubers, marketers, content creators u...

Security Scan

The skill's requested token and APIs align with its video-rendering purpose; it directs uploads and rendering to an external service, so review privacy and trust in that service before using.

Purpose & Capability

Name/description (generate video scripts and cloud-render MP4s) lines up with the single required credential (NEMO_TOKEN) and the runtime behavior described (session creation, uploads, render/export). No unrelated cloud credentials or binaries are requested.

Instruction Scope

The SKILL.md instructs the agent to POST user-provided files and messages to https://mega-api-prod.nemovideo.ai, create sessions, stream SSE chat, poll render status, and return download URLs. This is consistent with a cloud render pipeline, but it means user files (up to 200MB) and any prompt/brief text will be transmitted to that third-party service. The metadata declares a config path (~/.config/nemovideo/) which is not extensively referenced in the prose — minor mismatch but plausible (e.g., local token/cache).

Install Mechanism

There is no install spec and no code files; this is instruction-only. Nothing is downloaded or written by an installer according to the package metadata.

Credentials

Only NEMO_TOKEN (primaryEnv) is required, which is appropriate for a service that needs authorization. The skill also supports acquiring an anonymous token if none is present. Be aware that any valid NEMO_TOKEN grants bearer access to the remote rendering/credits API — treat it like a service credential. The declared config path (~/.config/nemovideo/) may allow the agent to locate local stored tokens or settings; the SKILL.md does not fully justify the need for that path but its presence is plausible.

Persistence & Privilege

always is false and the skill does not request elevated or persistent platform-wide privileges. Autonomous invocation is allowed (platform default) but there is no indication the skill modifies other skills or system-wide configs.

Assessment

This skill appears to do what it says: it will send your brief/files to the nemo video backend and return rendered video URLs. Before installing or using it: (1) Confirm you trust the domain https://mega-api-prod.nemovideo.ai and its privacy/terms (your uploaded media and prompts are transmitted there). (2) Treat NEMO_TOKEN like an API key — only provide a token you trust the service with; consider using the anonymous token for trials. (3) Don’t upload sensitive personal data or private keys as part of prompts/files. (4) If you want more assurance, ask the publisher for a homepage, privacy policy, or source code, or run the skill in a controlled environment and monitor network activity. If you want, I can list specific questions to ask the publisher or suggest safer alternatives for local-only script generation.

Getting Started

Share your text or brief and I'll get started on AI script generation. Or just tell me what you're thinking.

Try saying:

• "generate my text or brief"
• "export 1080p MP4"
• "write a video script for a"

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.

Video Script — Generate Scripts for Videos

Drop your text or brief in the chat and tell me what you need. I'll handle the AI script generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 60-second product explainer brief, ask for write a video script for a 90-second tutorial on how to use our app, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — include your target audience in the prompt for a more tailored tone and pacing.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-script, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

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.

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 → "write a video script for a 90-second tutorial on how to use our app" → Download MP4. Takes 20-40 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 video script for a 90-second tutorial on how to use our app" — concrete instructions get better results.

Max file size is 200MB. Stick to TXT, DOCX, PDF, MP4 for the smoothest experience.

Export as MP4 for widest compatibility.