Text To Video Ki

Turn a short paragraph describing a product launch scene into 1080p AI generated videos just by typing what you need. Whether it's generating videos from wri...

Security Scan

The skill's declared purpose (text→video) matches its runtime instructions and required credential (NEMO_TOKEN); there are minor metadata inconsistencies and privacy considerations (it uploads user media to an external API) but nothing that indicates the skill is trying to do something unrelated to its stated purpose.

Purpose & Capability

Name/description, required credential (NEMO_TOKEN), and the SKILL.md behavior all align: the skill talks to a cloud video-rendering backend, uploads media, creates render jobs, polls for results, and returns download URLs. One inconsistency: the registry metadata lists no required config paths, but the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/). This is likely a metadata mismatch but not a functional mismatch with the stated purpose.

Instruction Scope

Instructions are concrete and scoped to cloud rendering: check NEMO_TOKEN, optionally obtain an anonymous token via an API call, create sessions, handle SSE, upload files, poll export status, and return download links. The skill will read/derive an install path to set an X-Skill-Platform header and references a user config directory. It does not instruct reading unrelated system files or other credentials. It will upload user-provided media to the remote service — expected for this functionality but a privacy consideration.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk or fetched by an installer. Lowest install risk.

Credentials

Only NEMO_TOKEN is declared as required and used as a Bearer token for API calls. The SKILL.md also supports generating an anonymous token if NEMO_TOKEN is absent (via a POST to the service). No unrelated secrets or multiple credentials are requested. The configPaths entry in the frontmatter (not reflected in registry metadata) suggests the skill may look in ~/.config/nemovideo/ for local state, which is plausible for this service but should be noted.

Persistence & Privilege

always is false and the skill is user-invocable; it does not demand forced inclusion or elevated platform privileges. The skill manages its own session and tokens for the remote service, which is normal for this type of integration.

Assessment

This skill appears to do what it says: it sends your text and any media you provide to a remote video-rendering service (mega-api-prod.nemovideo.ai) and returns a downloadable video. Before installing or using it, consider: 1) Privacy — uploaded media will be sent to an external service; don't upload sensitive content unless you trust the service and its policies. 2) Token handling — the skill accepts a NEMO_TOKEN you provide or will obtain an anonymous token for you; providing your own token gives the service access tied to that token, while anonymous tokens have limited credits. 3) Metadata mismatch — the SKILL.md mentions a config path (~/.config/nemovideo/) that the registry metadata did not; this is likely benign but note the skill may read that folder. 4) Source trust — there is no homepage or known publisher in the registry entry; if you require stronger assurance, ask the publisher for a homepage, privacy policy, or source code before proceeding.

Getting Started

Share your text prompt and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "convert my text prompt"
• "export 1080p MP4"
• "convert this text description into a"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Text to Video KI — Generate Videos from Text

Drop your text prompt 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 short paragraph describing a product launch scene, ask for convert this text description 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 and more specific text prompts produce more accurate video results.

Matching Input to Actions

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

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

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.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "convert this text description 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.