Best Text To Video Ai

convert text prompts into AI generated videos with this skill. Works with TXT, DOCX, PDF, SRT files up to 200MB. marketers use it for generating videos from...

Security Scan

The skill's behaviour (uploading files and calling a remote API) matches its description, but inconsistencies in declared config paths and instructions that may probe local paths and upload user files to an external endpoint make the package worth extra scrutiny before use.

Purpose & Capability

The declared primary credential (NEMO_TOKEN) and the runtime instructions that call a remote video-rendering API are consistent with a text-to-video service. Nothing else (no extra cloud credentials or unrelated binaries) is requested. However, the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) that is not reflected in the registry metadata — an inconsistency that suggests the skill may expect or touch a local config directory even though the registry did not declare it.

Instruction Scope

Runtime instructions direct the agent to POST to https://mega-api-prod.nemovideo.ai for anonymous tokens, session creation, SSE streaming, uploads, and exports — which is expected for this service. They also instruct generating a client UUID, streaming SSE connections, and uploading files via multipart using local file paths (e.g., -F "files=@/path"). The SKILL.md further instructs detecting an installation path (~/.clawhub/ or ~/.cursor/skills/) to set a header. That implies the agent may probe home-directory paths and access local files beyond the user-supplied upload, and it instructs keeping technical details out of chat (which could hide network activity). These behaviors are plausible for a file-uploading service but broaden the agent's access surface and should be confirmed with the publisher.

Install Mechanism

There is no install spec and no code files; this is an instruction-only skill. That limits on-disk changes and reduces install-time risk.

Credentials

Only NEMO_TOKEN is required, which is appropriate for a service API key. However, the skill's YAML metadata also lists a config path (~/.config/nemovideo/) and the runtime docs describe detecting install paths to set X-Skill-Platform headers. The registry metadata (provided separately) did not declare these config paths. The mismatch means the agent may access or expect files in your home directory even though that access wasn't declared up front — a disproportionate/unclear usage of local config paths that should be clarified.

Persistence & Privilege

The skill does not request 'always: true' and has no install steps that would permanently modify agent configuration. It does create session tokens and may store or use a token (NEMO_TOKEN) during operation; the frontmatter's config path suggests it could read/write ~/.config/nemovideo/ if implemented. Confirm whether tokens or artifacts are persisted and where.

What to consider before installing

What to consider before installing/using this skill: - The skill will upload your files and prompts to https://mega-api-prod.nemovideo.ai for cloud rendering and return download URLs — do not upload sensitive or confidential content unless you trust the service and its privacy policy. - It needs a NEMO_TOKEN (API token). If none is present it will create an anonymous token for you by calling the service; consider using a throwaway token if you want to limit exposure. - The SKILL.md suggests detecting install paths and references a local config directory (~/.config/nemovideo/). The registry metadata did not declare this; ask the publisher to confirm whether the skill will read/write those paths and why. - Because this is an instruction-only skill with no code to review, you cannot audit exactly what it will read or send. If you need stronger assurance, request the skill's source or prefer a reviewed client or official integration. - If you decide to use it: avoid uploading secrets or private files, monitor network activity if possible, and consider creating an account/token with limited privileges or a short lifetime. If you want, I can: 1) draft questions to ask the skill author about the config path and persistence, or 2) walk through what a minimal safety checklist would look like before sending files to the service.

Getting Started

Ready when you are. Drop your text prompts here or describe what you want to make.

Try saying:

• "convert a 150-word product description paragraph into a 1080p MP4"
• "turn this script into a 30-second video with visuals and background music"
• "generating videos from written scripts or text prompts for marketers"

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.

Best Text to Video AI — 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 150-word product description paragraph and want to turn this script 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 scripts under 100 words produce faster and more focused videos.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is best-text-to-video-ai, 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).

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

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.

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 script 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 and web platforms.

Common Workflows

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