Text To Video Narration Ai

convert text script into narrated video files with this skill. Works with TXT, DOCX, PDF, SRT files up to 200MB. marketers use it for turning written scripts...

Security Scan

The skill's claimed purpose (convert scripts to narrated video) matches its network/API usage, but there are inconsistencies (metadata vs. registry), an unknown backend domain, and instructions that may read local install/config paths — all of which warrant caution before installing or providing credentials.

Purpose & Capability

The name/description (text → narrated video) aligns with the declared single credential NEMO_TOKEN and the SKILL.md which describes calls to a cloud render API. However the SKILL.md metadata lists a local config path (~/.config/nemovideo/) while the registry declared no required config paths — this mismatch is unexplained and worth clarifying.

Instruction Scope

Instructions are primarily network calls to an external API (auth, session creation, upload, SSE for streaming, render/export). These are expected for a cloud-rendering service. The SKILL.md also instructs the agent to detect an install path to set an X-Skill-Platform header and references a local config directory; that requires reading local paths and is not strictly necessary for core functionality — this is scope creep that should be justified. There are no instructions to read arbitrary user files beyond the user-supplied uploads.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. That lowers risk compared to skills that download or execute third-party code.

Credentials

The skill requests a single credential (NEMO_TOKEN) which is proportionate to a cloud API client. The SKILL.md also describes generating an anonymous NEMO_TOKEN if none is present. The metadata's mention of a local config path (~/.config/nemovideo/) suggests potential file access not declared in the registry; that inconsistency should be clarified. No other secrets are requested.

Persistence & Privilege

always is false and the skill does not request system-level persistence or modification of other skills. It relies on autonomous invocation (platform default), which increases blast radius only if combined with other risks — here that combination is possible but not definitive.

Scan Findings in Context

[no-code-to-scan] expected: The regex scanner had no code files to analyze. For instruction-only skills this is expected, but it means runtime behavior is defined solely by the SKILL.md text and external API interactions.

What to consider before installing

This skill mostly does what it says (talks to a cloud video-rendering API and needs a NEMO_TOKEN), but exercise caution because: 1) the skill's registry metadata and SKILL.md disagree about a local config path (~/.config/nemovideo/) — ask the publisher why the skill might read that directory; 2) the backend domain (mega-api-prod.nemovideo.ai) and owner are not otherwise documented — verify the service and its privacy/security practices before sending sensitive content; 3) the skill will upload your script/media (up to 200MB) to the cloud and can generate or use an anonymous token with 7-day expiry — test with non-sensitive data first; 4) avoid supplying unrelated secrets or system credentials. If you go ahead: request confirmation from the maintainer about where (if anywhere) tokens or session info are stored, run an initial test with dummy content, and be prepared to revoke or rotate any token you provide.

Getting Started

Got text script to work with? Send it over and tell me what you need — I'll take care of the AI narration video generation.

Try saying:

• "convert a 200-word product description script into a 1080p MP4"
• "convert this script into a narrated video with matching visuals"
• "turning written scripts into AI-narrated videos for marketers"

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.

Text to Video Narration AI — Convert Scripts into Narrated Videos

This tool takes your text script and runs AI narration video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 200-word product description script and want to convert this script into a narrated video with matching visuals — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 150 words produce the most natural-sounding narration.

Matching Input to Actions

User prompts referencing text to video narration ai, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is text-to-video-narration-ai, 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).

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "convert this script into a narrated video with matching visuals" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social and presentation platforms.

Common Workflows

Quick edit: Upload → "convert this script into a narrated video with 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.