Text To Video Explainer

convert written text script into animated explainer video with this skill. Works with TXT, DOCX, PDF, SRT files up to 10MB. marketers, educators, startup fou...

Security Scan

The skill's requested credential and runtime actions match its stated purpose (uploading scripts and calling a cloud render API); nothing obviously disproportionate or malicious is present, though a few minor inconsistencies and privacy considerations are worth noting.

Purpose & Capability

Skill claims to convert text to video and only requests a single service credential (NEMO_TOKEN) and cloud API endpoints that align with video rendering, uploads, session and export operations.

Instruction Scope

The SKILL.md contains concrete API workflows (session creation, SSE, upload, export) consistent with the described cloud service. It instructs uploading user files (multipart or URL) and polling session state. It also references detecting install paths and a local config path in frontmatter; the instructions don't explicitly tell the agent to read arbitrary unrelated files, but the install-path detection and declared configPaths (~/.config/nemovideo/) could lead the agent to inspect the user's home config if implemented — this is a privacy concern to be aware of.

Install Mechanism

There is no install script or binary download (instruction-only), so nothing is written to disk by the skill itself. This is the lowest-risk install footprint.

Credentials

Only NEMO_TOKEN is required which is proportionate for a cloud video service. The SKILL.md also documents an anonymous-token flow if NEMO_TOKEN is not present (POST to the service to obtain a short-lived token). However, the frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported none — that mismatch could lead to reading an existing token/sensitive files if the agent implements those steps.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or persistent platform-wide privileges. Autonomous invocation is allowed (platform default) and appropriate for this type of skill.

Assessment

This skill appears to do what it says: it uploads your script and files to an external video-rendering backend that requires a NEMO_TOKEN. Before installing or using it, consider: 1) Any files you drop into the skill will be sent to mega-api-prod.nemovideo.ai — do not upload sensitive data you would not want shared. 2) The skill will use NEMO_TOKEN; if you don't already have one it will obtain an anonymous short-lived token itself — prefer using a scoped/ephemeral token rather than a long-lived secret. 3) The frontmatter mentions a local config path (~/.config/nemovideo/) and install-path detection; ask the author whether the agent will read that directory or any local files (the SKILL.md does not clearly require reading those files). 4) There is no source/homepage listed — if you need stronger assurance, ask the publisher for source code or a privacy policy and confirm the token scope and retention policy. If you accept those privacy trade-offs and are comfortable with sending media to their cloud, the skill is coherent with its stated purpose.

Getting Started

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

Try saying:

• "convert my written text script"
• "export 1080p MP4"
• "turn this script into an explainer"

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 Explainer — Turn Scripts into Explainer Videos

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

Here's a typical use: you send a a 200-word product explanation script, ask for turn this script into an explainer video with voiceover and animated slides, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter scripts under 150 words produce tighter, more engaging explainer videos.

Matching Input to Actions

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

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

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.

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

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this script into an explainer video with voiceover and animated slides" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across websites, presentations, and social platforms.

Common Workflows

Quick edit: Upload → "turn this script into an explainer video with voiceover and animated slides" → 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.