Ai Video Gen Script

Turn a 200-word product launch script into 1080p script-based videos just by typing what you need. Whether it's generating videos automatically from written...

Security Scan

The skill's runtime instructions generally match a cloud video-generation service, but there are internal inconsistencies (declared required env/config vs. the skill's anonymous-token flow and metadata mismatches) and it will send user scripts/files to an external service you should verify before using with sensitive data.

Purpose & Capability

The skill's description (convert scripts to videos) aligns with the API calls and endpoints in SKILL.md. However, the registry declares NEMO_TOKEN as required while the SKILL.md explicitly supports generating an anonymous token if NEMO_TOKEN is not present — this is an incoherence (the env var is marked required but the skill can operate without it). The SKILL.md also lists a config path (~/.config/nemovideo/) in its frontmatter while the registry report lists no required config paths.

Instruction Scope

The instructions confine activity to the external nemovideo API: session creation, SSE chat, uploads, state, credits, and export. There are no directives to read arbitrary system files or unrelated credentials. The only system interaction implied is detecting an install path to set an attribution header and an optional config path in metadata; these are plausible for attribution but should be explicitly confirmed.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is downloaded or written by an installer. This is low-risk from an install/execution standpoint.

Credentials

Only one credential (NEMO_TOKEN) is declared, which is appropriate for calling the external API. But the SKILL.md's ability to obtain an anonymous NEMO_TOKEN at runtime makes the declared 'required' nature of the env var misleading. The frontmatter also references a config path where tokens might be stored — the skill does not explicitly document writing there, so verify whether tokens or metadata are persisted to ~/.config/nemovideo/.

Persistence & Privilege

The skill is not force-installed (always:false) and uses normal autonomous invocation settings. It does not request special persistent system privileges in the SKILL.md. Be aware it will create and use session tokens and may orphan server-side jobs if a session is closed mid-render (documented behavior).

What to consider before installing

What to consider before installing: - This skill will send any provided script and uploaded media to https://mega-api-prod.nemovideo.ai for cloud rendering. Do not send sensitive or private content unless you trust that service and have reviewed its privacy/terms. - The registry says NEMO_TOKEN is required, but the skill can fetch an anonymous token itself if NEMO_TOKEN is absent — ask the publisher which behavior is intended and whether anonymous tokens or acquired tokens are ever persisted locally (SKILL.md mentions a config path in its frontmatter). - Confirm what (if anything) is written to ~/.config/nemovideo/ or other local paths and how long anonymous tokens remain valid. - Verify the service domain (mega-api-prod.nemovideo.ai) — there is no homepage or source listed in the registry, which reduces transparency. If you need stronger assurance, request the author's source code or a homepage, test with non-sensitive sample content, and consider using an account-specific token rather than environment-wide secrets. - Overall: functionally coherent for a cloud video service, but the metadata/env inconsistencies and lack of publisher/source information justify caution.

Getting Started

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

Try saying:

• "generate my text script"
• "export 1080p MP4"
• "turn this script into a video"

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.

AI Video Gen Script — Generate Videos From Scripts

Send me your text script and describe the result you want. The AI video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 200-word product launch script, type "turn this script into a video with voiceover and matching visuals", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter scripts under 300 words render noticeably faster.

Matching Input to Actions

User prompts referencing ai video gen 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 ai-video-gen-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)

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

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 → "turn this script into a video with voiceover and matching visuals" → 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 "turn this script into a video with voiceover and matching visuals" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.