Free Text To Video Best

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

Security Scan

The skill's requirements and runtime instructions are consistent with a text-to-video API client: it asks only for an API token, streams/uploads user content to a remote rendering service, and has no install step or extra credentials — but it will send your text/files to an external service and store session tokens locally, so review privacy/ trust before using.

Purpose & Capability

Name/description (convert text to short videos) align with required credential (NEMO_TOKEN) and the API endpoints in SKILL.md. The skill declares a nemovideo config path in its YAML metadata which matches the service it calls, so access requests are proportionate to its stated purpose. (Note: registry metadata at the top said no required config paths while the SKILL.md metadata lists one — minor inconsistency.)

Instruction Scope

Runtime instructions are focused on authenticating, creating a session, uploading user files, streaming SSE for generation, polling render status, and exporting — all expected for a cloud render client. The SKILL.md also documents generating an anonymous token flow and saving the session_id/token locally and instructs deriving attribution headers by checking install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) — this requires reading those filesystem paths. Nothing in the instructions directs the agent to read unrelated secrets or system files beyond that.

Install Mechanism

No install spec or code files (instruction-only), so nothing is downloaded or written to disk by an installer. Lower install risk.

Credentials

Only a single credential (NEMO_TOKEN) is required and it's clearly the API bearer token used for the described endpoints. The SKILL.md also supports an anonymous-token flow which issues a short-lived token. No unrelated credentials or broad access variables are requested. Minor note: the YAML frontmatter mentions a config path (~/.config/nemovideo/) which implies reading/storing local config, but that is consistent with the service.

Persistence & Privilege

Skill does not request always:true or elevated platform-wide privileges. It instructs saving session_id and token state locally (normal for a session-based API client). It does not direct modifications to other skills or global agent configs.

Assessment

This skill appears to be a thin client for a third-party text-to-video service and is internally consistent. Before installing or using it, consider: 1) All text and uploaded files will be sent to https://mega-api-prod.nemovideo.ai — do not send sensitive or private data. 2) The skill will store short‑lived tokens and a session_id locally; treat these like credentials and delete/rotate them if needed. 3) If you don't already have a NEMO_TOKEN, the skill can mint an anonymous token (100 credits, 7‑day expiry) — prefer a throwaway token for testing. 4) The SKILL.md infers install-paths (~/.clawhub, ~/.cursor) to populate attribution headers — this requires checking those paths and is minor privacy exposure. 5) Verify the service's privacy/terms and the domain before sending proprietary material. If any of these are unacceptable, do not install or only use with non-sensitive test 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:

• "convert a 100-word product description paragraph into a 1080p MP4"
• "convert this blog intro into a 30-second video with visuals and background music"
• "generating videos from written text or scripts for marketers, content creators, educators"

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 — 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 100-word product description paragraph, type "convert 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 prompts produce more accurate and focused video results.

Matching Input to Actions

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

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

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

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)

Common Workflows

Quick edit: Upload → "convert 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 "convert 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, plain text for the smoothest experience.

Export as MP4 for widest compatibility across platforms and devices.