Text To Video App

Skip the learning curve of professional editing software. Describe what you want — turn this blog intro into a 30-second video with voiceover and visuals — a...

Security Scan

The skill's behavior (uploading text/files and contacting a remote nemovideo.ai API) is coherent with a text-to-video service, but there are internal inconsistencies about required credentials/config paths and several privacy/telemetry implications you should understand before installing.

Purpose & Capability

Name/description match the instructions: the skill routes user text/files to a remote video-rendering API. Requesting a service token (NEMO_TOKEN) is proportionate. However, the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) that the registry metadata did not list, and the SKILL.md also documents a fallback anonymous-token flow — so the manifest and runtime docs disagree about whether a persistent token/config is required.

Instruction Scope

All instructions describe expected API flows (session creation, SSE, upload, export). These stay within the stated purpose, but they explicitly instruct the agent to send user-provided files (up to 200MB) and metadata to a third-party domain (mega-api-prod.nemovideo.ai). The skill also asks for constructing attribution headers (X-Skill-Platform) by inspecting install path patterns, which implies the agent may inspect environment/install paths to populate headers.

Install Mechanism

Instruction-only skill with no install spec and no included code — no additional software is written to disk by the skill itself.

Credentials

Only one credential (NEMO_TOKEN) is declared, which is appropriate for an API-backed service. But SKILL.md explicitly supports generating an anonymous token if NEMO_TOKEN is absent, contradicting the registry's 'required env var' claim. The skill also instructs including attribution headers that may reveal platform/install-path details.

Persistence & Privilege

always=false and there is no install or code writing to agent configs. The skill does not request permanent presence or modification of other skills.

What to consider before installing

This skill will send whatever text and uploaded files you provide to a remote service at mega-api-prod.nemovideo.ai for rendering — treat that as data exfiltration to a third party. The manifest claims NEMO_TOKEN is required, but SKILL.md documents a fallback anonymous-token flow and also references a local config path in its frontmatter; those inconsistencies mean the publisher metadata may be out of sync with the runtime instructions. Before installing or using: (1) avoid uploading sensitive or confidential text/files unless you trust the nemovideo.ai service and its privacy policy; (2) prefer using a disposable or limited token if you must set NEMO_TOKEN; (3) ask the publisher for provenance (owner identity, homepage, privacy/TOS) and clarification about the config path and whether persistent credentials are stored locally; (4) be aware the skill will include attribution headers that can reveal platform/install-path hints — if that is a concern, get clarification about what the headers contain. Providing that additional provenance and clarification could raise confidence to benign; without it, treat the mismatches and external data flow as a risk.

Getting Started

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

Try saying:

• "convert a 150-word product description into a 1080p MP4"
• "turn this blog intro into a 30-second video with voiceover and visuals"
• "converting written content into short social media videos for content creators"

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.

Text to Video App — Convert Text into Shareable Videos

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

A quick example: upload a 150-word product description, type "turn this blog intro into a 30-second video with voiceover and visuals", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter, clearer text produces more accurate visuals and smoother voiceover sync.

Matching Input to Actions

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

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)

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

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.

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 blog intro into a 30-second 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 blog intro into a 30-second video with voiceover and 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 platforms and video hosts.