Text To Video In Free

generate text prompts into ready-to-share videos with this skill. Works with TXT, DOCX, PDF, SRT files up to 200MB. content creators, marketers, students use...

Security Scan

The skill's requirements and runtime instructions are broadly consistent with a text→video cloud-rendering integration, but there are small metadata inconsistencies and privacy-related details you should review before installing.

Purpose & Capability

Name/description (text→video conversion) match the instructions and endpoints (nemovideo.ai). Requesting a service token (NEMO_TOKEN) is expected for a cloud API. Note: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this mismatch should be reconciled.

Instruction Scope

Instructions stay within the stated purpose (create sessions, upload user files, stream SSE, start renders, poll state). They direct the agent to upload user files (up to 200MB) and to call external API endpoints. The skill also instructs the agent to detect an install path (to set X-Skill-Platform), which implies probing the filesystem for well-known directories; this is reasonable for attribution but is a privacy-relevant action to be aware of. The skill does not instruct reading arbitrary unrelated system files or other credentials.

Install Mechanism

Instruction-only skill with no install spec and no code files — low install risk. Nothing is downloaded or written by an installer step according to the provided metadata.

Credentials

Only NEMO_TOKEN is required and is appropriate for a single cloud API. However the SKILL.md frontmatter/metadata references a config path (~/.config/nemovideo/) which could imply reading local config; the registry metadata elsewhere indicated none. This inconsistency should be clarified because access to config paths can expose credentials or local data.

Persistence & Privilege

always:false and no install step mean the skill does not request permanent, forced inclusion or elevated platform privileges. The skill does instruct creating/storing an anonymous token and a session_id for requests (normal for API usage).

Assessment

This skill appears to be what it says: a cloud-based text→video converter that uses a single API token (NEMO_TOKEN) and uploads user files to https://mega-api-prod.nemovideo.ai. Before installing, confirm you trust that domain and are comfortable with the skill uploading files (up to 200MB). Ask the publisher to explain the metadata mismatch about ~/.config/nemovideo/ (registry said none, SKILL.md lists it) — clarify whether the skill will read that path. Be aware the skill will generate or request an anonymous token on your behalf and will send that token in Authorization headers to the nemovideo API; do not provide other secrets. If you need higher assurance, request the skill source or an official homepage, or run the skill in a restricted environment/network or inspect network traffic to confirm behavior.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "turn this text into a 30-second"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Text to Video Free — Convert Text into Shareable Videos

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

Say you have a 50-word product description and want to turn this text into a 30-second video with visuals and background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter text inputs under 100 words produce faster and more focused video outputs.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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-in-free, 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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this text into a 30-second video with visuals and background music" — 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 devices.

Common Workflows

Quick edit: Upload → "turn this text 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.