Free Text To Video Online

convert text prompt into ready-to-share videos with this skill. Works with TXT, DOCX, PDF, copied text files up to 500MB. marketers, bloggers, social media c...

Security Scan

The skill's requests and runtime instructions are coherent with a text→video cloud-rendering service: it only asks for a single service token and describes calling that service's APIs; nothing obvious is disproportionate or unrelated to its stated purpose.

Purpose & Capability

Name/description (text→video) align with the single required credential (NEMO_TOKEN) and the declared config path (~/.config/nemovideo/). Required env/config items are what you'd expect for a hosted rendering service.

Instruction Scope

The SKILL.md instructs the agent to obtain or use NEMO_TOKEN, create sessions, send SSE chat messages, upload files, poll exports and handle download URLs — all consistent with a remote render API. One minor scope note: the doc suggests detecting install path to set X-Skill-Platform (checking for ~/.clawhub/ or ~/.cursor/skills/) which implies probing local filesystem paths; this is small and explainable but is not declared as a required config path. The skill also instructs saving session_id (expected) but does not specify where or how it will be persisted.

Install Mechanism

Instruction-only skill with no install spec or code files; nothing is written to disk by an installer. This is the lowest-risk install profile.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv). The token is justified by the API interactions described; no unrelated credentials or broad secrets are requested.

Persistence & Privilege

always is false and there is no install-time modification of other skills or system settings. The skill requires a session token to interact with the service (session_id) but does not request elevated or persistent platform privileges.

Assessment

This skill appears coherent for a cloud text→video service, but before installing consider: 1) NEMO_TOKEN (or the anonymous token obtained) grants the skill access to your account/credits — treat it like any API key and only provide it to services you trust. 2) The skill uploads user files (up to 500MB) to an external domain (mega-api-prod.nemovideo.ai) — do not upload sensitive or confidential material unless you accept the privacy/retention policy of that service. 3) The SKILL.md suggests probing common install directories to set an attribution header — if you are uncomfortable with any local path checks, ask for clarification or restrict the agent's filesystem access. 4) If you require tighter control, create a limited/ephemeral NEMO_TOKEN (or use anonymous tokens) and monitor exported URLs/credits. Overall this looks internally consistent, but verify the legitimacy and privacy practices of the nemovideo endpoint before use.

Getting Started

Ready when you are. Drop your text prompt 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 visuals and background music"
• "generating videos from written content without recording footage for marketers, bloggers, social media creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Free Text to Video Online — Convert Text into Shareable Videos

Send me your text prompt 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-200 words per video.

Matching Input to Actions

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

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

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.

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 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 websites.

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.