Free Text To Video Ki

convert text prompts into AI-generated videos with this skill. Works with TXT, DOCX, PDF, plain text files up to 500MB. marketers, content creators, educator...

Security Scan

The skill's requirements and runtime instructions are largely coherent with a text→video API client, but there are minor metadata mismatches and external-network behaviors you should understand before installing.

Purpose & Capability

Name and description (convert text prompts into videos) match the runtime instructions (session creation, SSE chat, upload, export). Requesting a single API token (NEMO_TOKEN) is consistent with a cloud-render service. However, the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) while the registry metadata earlier listed no required config paths — a small inconsistency worth clarifying.

Instruction Scope

Instructions describe only API interactions with a single external service (mega-api-prod.nemovideo.ai): auth, session creation, SSE, upload, status, export. They do not instruct reading arbitrary unrelated files or other environment secrets. The skill asks agents to detect install path to set an X-Skill-Platform header (reading an install path is minor and understandable for attribution) and to send attribution headers; these are within the scope of a client SDK.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is downloaded or written by an installer. That is the lowest-risk install model.

Credentials

Only one credential (NEMO_TOKEN) is declared as primary, which fits the described API usage. Two points to watch: (1) SKILL.md includes a config path (~/.config/nemovideo/) which could contain additional credentials/config — the registry metadata did not declare this path; (2) if NEMO_TOKEN is absent the instructions tell the agent to obtain an anonymous token by POSTing to an external endpoint, which means the agent will always make outbound network requests during auth if no token is present. Both behaviors are explainable but should be explicit to users.

Persistence & Privilege

always:false and user-invocable:true. The skill does not request system-wide configuration changes nor does it claim permanent presence. Autonomous invocation (model invocation enabled) is platform default and not by itself a red flag here.

Assessment

This skill appears to be an API client for a third‑party service (nemovideo.ai). Before installing: 1) Confirm you trust mega-api-prod.nemovideo.ai / nemovideo.ai and understand their privacy/terms — the skill will send your prompts and uploaded files to that service. 2) Prefer using a scoped/ephemeral NEMO_TOKEN you control; avoid putting broad or long‑lived credentials in the agent environment. 3) Ask the publisher to explain the config path (~/.config/nemovideo/) declared in the skill frontmatter (registry metadata omitted it) — clarify whether the agent will read files there. 4) If you’re cautious, test using the anonymous-token flow (no NEMO_TOKEN) first and monitor network activity and any created jobs/credits. 5) If you need higher assurance, request a source/homepage or review source code before granting access to sensitive environments.

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.

Free Text to Video AI — Convert Text into AI 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 two-sentence 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, clearer text prompts produce more accurate video results.

Matching Input to Actions

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

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)

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

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, plain text for the smoothest experience.

Export as MP4 for widest compatibility.

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.