Text To Video Explanation

Skip the learning curve of professional editing software. Describe what you want — turn this text into a short explainer video with voiceover and visuals — a...

Security Scan

The skill mostly matches its stated purpose (convert text to video) but contains behavioral inconsistencies and data-flow decisions that deserve caution before use.

Purpose & Capability

The skill's name and description (text → explainer video) align with the APIs and endpoints documented in SKILL.md. However, metadata lists NEMO_TOKEN as a required credential while the runtime instructions explicitly implement an anonymous-token fallback via an external API — a mismatch between 'required' and 'optional/auto-provisioned' credential handling.

Instruction Scope

Runtime instructions tell the agent to: 1) look for NEMO_TOKEN, 2) if missing, call an external anonymous-token endpoint and adopt that token, 3) create sessions and POST/GET against mega-api-prod.nemovideo.ai, 4) read this file's YAML frontmatter for attribution, and 5) detect install path (~/.clawhub/ or ~/.cursor/) to set headers. These actions include network calls that will upload user files and local filesystem checks (to detect install path and a config path), which go beyond simple text processing and could expose user files or local metadata to a third-party service.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing is written to disk by an installer. This is a lower-risk distribution model; the main risk is runtime network activity described in SKILL.md.

Credentials

The skill requests a single credential (NEMO_TOKEN), which is appropriate for a cloud API. But it also instructs obtaining an anonymous token from an external endpoint when NEMO_TOKEN is missing, and metadata declares a configPath (~/.config/nemovideo/). The combination means the skill may read local config and will call an external auth endpoint on its own, potentially creating/using tokens without explicit user-provided credentials — this is unexpected given the 'required env' declaration and should be clarified.

Persistence & Privilege

The skill is not marked always:true and does not request system-wide persistence. It stores only session IDs for operation and does not declare modification of other skills or system settings in SKILL.md.

What to consider before installing

This skill will upload your text and any files you provide to an external service (mega-api-prod.nemovideo.ai) to produce videos. Before installing or using it: 1) Decide if you trust that external service with any content (do not upload sensitive PII, secrets, or proprietary files unless you trust their privacy/security). 2) Note the skill asks for NEMO_TOKEN but will also request an anonymous token from the service if you don't supply one — that means it can initiate network auth on its own. 3) The skill will check certain local paths (install detection and ~/.config/nemovideo/) to construct headers; verify whether those files contain credentials you don't want read. 4) If you plan to supply your own NEMO_TOKEN, only do so if you trust the service and understand its token scope and expiry. 5) If you need higher assurance, ask the publisher for: a privacy/security policy, the exact schema of any files uploaded, and confirmation whether any local files/credentials are read or logged. If you can't get those answers, treat this skill as untrusted and avoid sending sensitive content.

Getting Started

Ready when you are. Drop your written text here or describe what you want to make.

Try saying:

• "convert a 200-word product explanation paragraph into a 1080p MP4"
• "turn this text into a short explainer video with voiceover and visuals"
• "converting written explanations into narrated explainer videos for educators, marketers, content creators"

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 Explanation — Convert Text into Explainer Videos

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

Say you have a 200-word product explanation paragraph and want to turn this text into a short explainer video with voiceover and visuals — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter text blocks under 150 words produce tighter, more focused explainer videos.

Matching Input to Actions

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

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

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

• X-Skill-Source: text-to-video-explanation
• 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 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

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.

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

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

Export as MP4 for widest compatibility across platforms and devices.