Text To Ai

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

Security Scan

The skill's actions mostly match its stated purpose (converting text to videos), but there are small inconsistencies (a config path in the skill metadata that the registry doesn't declare) and the skill will call an external API and can obtain anonymous tokens — review before providing credentials or trusting the unknown source.

Purpose & Capability

Name/description align with the runtime instructions: the SKILL.md describes sending text to a remote rendering API and returning MP4s. The only requested credential is NEMO_TOKEN which matches the API usage. Minor inconsistency: the SKILL.md frontmatter metadata lists a config path (~/.config/nemovideo/) but the registry metadata shows no required config paths — this mismatch should be clarified.

Instruction Scope

Instructions are detailed and stay within the stated purpose (session creation, SSE messaging, uploads, export/polling). They instruct the agent to use NEMO_TOKEN if present or to POST for an anonymous token. They also instruct reading the SKILL.md frontmatter and detecting install path to set attribution headers. The skill does not instruct reading unrelated system files or other credentials, but the referenced config path in frontmatter implies it may check user config (~/.config/nemovideo/) which the registry did not declare.

Install Mechanism

No install spec and no code files — instruction-only skill. This is low-risk from an install standpoint (nothing is downloaded or written by the skill itself).

Credentials

Only one credential is declared (NEMO_TOKEN) which is appropriate for an API-backed video service. The SKILL.md also supports anonymous tokens obtained at runtime, so a provided NEMO_TOKEN is optional. Confirm whether the skill will read ~/.config/nemovideo/ or other config paths (frontmatter lists one) before supplying sensitive credentials.

Persistence & Privilege

The skill is not forced-always and does not request elevated persistent privileges. It does queue remote render jobs but does not request modification to other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says (send text to a cloud renderer and return video files) and is instruction-only (no installer or code). However: (1) the skill will call an external API (mega-api-prod.nemovideo.ai) and will either use your NEMO_TOKEN or fetch an anonymous token automatically — do not provide sensitive credentials unless you trust the service; (2) the SKILL.md metadata references a config path (~/.config/nemovideo/) that the registry did not declare — ask the publisher what it reads from that location; (3) the skill source is unknown and no homepage is provided, so prefer testing with non-sensitive/sample text first. If you decide to install, consider using the anonymous token path or a disposable project token rather than your primary account token.

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

Try saying:

• "convert a two-sentence product description into a 1080p MP4"
• "turn this text into a 30-second promotional video with visuals and music"
• "generating videos from written text or scripts 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.

Text to AI Video — Convert Text into Generated Videos

Send me your text prompts and describe the result you want. The AI video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a two-sentence product description, type "turn this text into a 30-second promotional video with visuals and 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 video results.

Matching Input to Actions

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

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

• X-Skill-Source: text-to-ai
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

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.

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

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)

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 text into a 30-second promotional video with visuals and 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.

Common Workflows

Quick edit: Upload → "turn this text into a 30-second promotional video with visuals and 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.