Text To Video Download Free

Turn a 150-word product description into 1080p downloadable MP4 videos just by typing what you need. Whether it's generating videos from written text or scri...

Security Scan

The skill's stated purpose (convert text to downloadable videos) is plausible and its single required credential (NEMO_TOKEN) is appropriate, but there are inconsistencies and filesystem/metadata accesses that aren't fully explained and warrant caution.

Purpose & Capability

The skill's capability (text→video via a cloud API) aligns with requiring a NEMO_TOKEN credential and calling the listed API endpoints. However, the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) that is not reflected in the registry metadata provided to you — this mismatch is an incoherence that should be clarified. Requiring a local nemovideo config file could be legitimate (to reuse stored tokens), but it should be declared consistently.

Instruction Scope

Runtime instructions ask the agent to read this file's YAML frontmatter and to detect the install platform by probing install paths (e.g., ~/.clawhub, ~/.cursor/skills). The frontmatter also lists a config path (~/.config/nemovideo/). Those filesystem checks go beyond simply calling the video API and could reveal presence of local config or other tooling. The SKILL.md does not explicitly limit what it will read from ~/.config/nemovideo/ (this could include tokens or user data). Also there are small inconsistencies in the error mapping (e.g., attribution header missing vs. HTTP 402), which suggests sloppy docs and increases risk of unexpected behavior.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That reduces risk compared with skills that download or install binaries.

Credentials

Only NEMO_TOKEN is declared as required, which is proportionate for a hosted video service. However, the SKILL.md frontmatter's configPaths entry implies the skill may also read a local config directory (potentially containing tokens or other sensitive info). The registry metadata you were given did not list config paths — this mismatch is a red flag to verify before granting access to local configs.

Persistence & Privilege

The skill is not marked always:true and uses default autonomous invocation settings. It does not request elevated system-wide persistence or modification of other skills' settings.

What to consider before installing

This skill appears to do what it says (use a NEMO_TOKEN to request video renders from a cloud API), but there are a few things to check before installing or running it: - Verify the service domain and operator: the API hostname (mega-api-prod.nemovideo.ai) and the skill owner are unknown — confirm this is a legitimate provider you trust. If you can't verify the vendor, be cautious. - Clarify the config path usage: ask whether the skill will read ~/.config/nemovideo/ and precisely what it will read from that directory. If it will access stored tokens or other secrets, prefer to supply only a scoped token rather than allowing arbitrary config access. - Be careful with NEMO_TOKEN: only provide a token with the minimal necessary scope and revoke it if you stop using the skill. If possible, use ephemeral/anonymous tokens created for this purpose rather than long-lived account credentials. - Request clarification on the metadata mismatch: the SKILL.md frontmatter lists required configPaths but the registry metadata did not — ask the publisher to fix this inconsistency before granting/configuring the skill. - If you are concerned about privacy, deny filesystem probing/installation-path detection or run the skill in an isolated environment where ~/.config and home paths do not contain sensitive data. If the publisher can confirm the configPaths usage and the service operator, and you can provide a limited-scope token, the skill is reasonable to use; otherwise treat it as untrusted.

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:

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

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 Download Free — Convert Text into Downloadable Videos

Drop your text prompts 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 150-word product description, ask for turn this text into a 30-second video with visuals and background music, 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 text inputs under 100 words produce faster and more focused videos.

Matching Input to Actions

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

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.

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

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

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)

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 500MB. Stick to TXT, DOCX, PDF, SRT for the smoothest experience.

Export as MP4 for widest compatibility across 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.