Text To Video Api

Turn a 200-word product description script into 1080p generated video files just by typing what you need. Whether it's generating videos programmatically fro...

Security Scan

The skill's instructions largely match a text→video API, but there are inconsistencies (metadata vs. frontmatter) and a few vague instructions that could require accessing agent install/config paths; verify the backend and token use before installing.

Purpose & Capability

Name/description (convert text scripts to 1080p video) align with the endpoints and workflows described in SKILL.md: session creation, SSE messages, upload, render/export. Requesting a single API token (NEMO_TOKEN) is expected for a cloud video service.

Instruction Scope

Instructions are primarily network calls to the nemovideo API (expected). However the frontmatter asks for configPaths (~/.config/nemovideo/) and requires detection of an install path to set X-Skill-Platform; it's unclear whether the agent must read filesystem/install paths to auto-detect platform. The doc also instructs to 'Keep the technical details out of the chat,' which reduces transparency about what data (session IDs, request failures) might be hidden from the user. Nothing in the instructions directs the agent to read unrelated system secrets, but the platform-detection step is vague and could imply reading environment/install metadata.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest install risk (no packages downloaded or archives extracted).

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which is appropriate for an API-based service. However there is an inconsistency: the registry metadata provided to you lists no required config paths, while the SKILL.md frontmatter includes ~/.config/nemovideo/ in metadata.requires.configPaths. That discrepancy should be resolved. Also, the skill recommends obtaining an anonymous token by POSTing to the vendor endpoint and then using that token as NEMO_TOKEN; consider using short-lived/anonymous tokens rather than uploading a long-lived secret, and verify what privileges that token grants and whether it will be stored.

Persistence & Privilege

always:false (no forced inclusion) and no install-time persistence are set. The skill can be invoked autonomously (default), which is normal for skills; this by itself is not a red flag. There is no indication the skill modifies other skills or system-wide settings.

Scan Findings in Context

[no_static_findings] expected: The regex-based scanner found no code files or matches. This is expected because the skill is instruction-only (SKILL.md). Absence of findings does not guarantee safety — behavior is determined by the runtime instructions (network calls).

What to consider before installing

This skill appears to be a straightforward wrapper for a third-party text→video API and requests a single API token (NEMO_TOKEN), which is reasonable. Before installing: 1) Verify the backend domain (mega-api-prod.nemovideo.ai) and the vendor's reputation — this skill will POST your scripts and media to that service. 2) Prefer using an anonymous/short-lived token (the skill supports generating one) rather than placing a long-lived secret in your environment. 3) Ask the author to clarify the config-path claim (~/.config/nemovideo/) and how X-Skill-Platform is auto-detected — confirm the skill will not read unrelated files or secrets. 4) Remember uploads may include sensitive content (product IP, audio), so check the vendor's retention and privacy policies. If you cannot verify the backend or resolve the metadata/configPath inconsistency, treat the skill cautiously.

Getting Started

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

Try saying:

• "convert my text prompts"
• "export 1080p MP4"
• "convert this script 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.

Text to Video API — Generate Videos from Text Scripts

Drop your text prompts in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 200-word product description script, ask for convert this script into a 30-second promotional video with visuals, and about 1-3 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter, structured scripts with clear scene breaks produce more accurate video output.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	text-to-video-api
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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.

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

Common Workflows

Quick edit: Upload → "convert this script into a 30-second promotional video with visuals" → Download MP4. Takes 1-3 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 script into a 30-second promotional video with visuals" — concrete instructions get better results.

Max file size is 500MB. Stick to TXT, DOCX, JSON, plain text for the smoothest experience.

Export as MP4 with H.264 encoding for broadest platform compatibility.