Text To Video Free

Get ready-to-share videos ready to post, without touching a single slider. Upload your text prompts (TXT, DOCX, PDF, copied text, up to 500MB), say something...

Security Scan

The skill's declared purpose (convert text to video) matches its runtime instructions and required credential (NEMO_TOKEN); it is an instruction-only integration that calls an external API and does not install software, but there are a few small documentation/information-flow inconsistencies to be aware of.

Purpose & Capability

The name/description (text→video) aligns with the actions in SKILL.md: creating sessions, uploading text/files, streaming SSE updates, rendering and returning download URLs. Required credential (NEMO_TOKEN) is appropriate for an API-backed service. Minor inconsistency: the registry metadata supplied to you lists no required config paths, but the SKILL.md frontmatter includes metadata that references a config path (~/.config/nemovideo/) and install-path detection for attribution headers. That difference is a documentation mismatch but does not by itself break purpose–capability alignment.

Instruction Scope

All instructions stay within the video-rendering workflow (auth, session creation, SSE messaging, uploads, polling render status, download). The skill explicitly instructs how to obtain an anonymous token if NEMO_TOKEN is missing, and how to upload local files (multipart -F 'files=@/path') which legitimately requires access to user-provided files. Two items to note: (1) the SKILL.md says to detect an install path (e.g., ~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform — that requires checking filesystem locations; (2) it instructs the agent to keep technical details out of chat, which can obscure network activity from user-visible messages. These are scope/visibility issues rather than outright abuse.

Install Mechanism

No install spec and no code files — the skill is instruction-only. That minimizes disk-writing/execution risk.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv). That is proportionate for an API-backed service. The SKILL.md also supports generating an anonymous token if no NEMO_TOKEN is present (network call to the service), which is reasonable. Again, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata did not — a minor inconsistency to clarify.

Persistence & Privilege

always:false (default) and no install-time persistence requested. The skill can be invoked autonomously per platform defaults, which is normal; nothing in the manifest attempts to force permanent inclusion or modify other skills' configs.

Assessment

This skill appears to do what it says: it will send your text/files to an external API (mega-api-prod.nemovideo.ai) to render videos and return download URLs. Before installing/using: (1) be comfortable that your content (up to 500MB) will be transmitted to that external service; avoid uploading sensitive data or secrets; (2) the skill will read an environment variable named NEMO_TOKEN if present — do not put unrelated credentials in that variable; (3) if no NEMO_TOKEN is present the skill will request an anonymous token from the service (7-day starter credits) — this is normal but still results in network activity; (4) the instructions may check common install/config paths to set attribution headers (this requires filesystem access) — if you prefer, run the skill in an environment where those paths are not present or where the agent is sandboxed; (5) there is a small metadata/documentation inconsistency (registry metadata vs SKILL.md configPaths) — if that matters to you, ask the publisher to clarify the intended config path access. If you need higher assurance, verify the service domain and privacy policy or limit uploads to non-sensitive content.

Getting Started

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

Try saying:

• "generate a 150-word product description into a 1080p MP4"
• "turn this blog intro into a 30-second video with visuals and background music"
• "generating videos from written content without recording footage for content creators, marketers, students"

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 Free — 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 visuals and background music", 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 — aim for 50-150 words per video.

Matching Input to Actions

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

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

• X-Skill-Source: text-to-video-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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.

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.

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

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)

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

Common Workflows

Quick edit: Upload → "turn this blog intro into a 30-second video with visuals and background music" → 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 visuals and background music" — 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 social platforms and devices.