Text To Video Mod

Turn a 150-word product description into 1080p generated video clips just by typing what you need. Whether it's converting written scripts or prompts into re...

Security Scan

The skill mostly does what its name says (call a nemo video API using NEMO_TOKEN), but there are a few metadata/instruction inconsistencies and some opaque guidance that merit caution before installing.

Purpose & Capability

Name/description align with the declared runtime behavior: it talks to a nemo video backend and requires a NEMO_TOKEN. However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata stated no required config paths — that mismatch is unexplained. Source/homepage are missing (unknown origin), which reduces ability to verify legitimacy.

Instruction Scope

Instructions are detailed and stay within the stated purpose (create sessions, upload video, SSE, poll export status). Two items to watch: (1) the SKILL.md instructs the agent to 'keep the technical details out of the chat' (this directs hiding internal actions from users), and (2) it asks the agent to 'auto-detect' platform from install path and enforces custom attribution headers — both are operationally plausible but add complexity and some opacity. The SKILL.md also prescribes obtaining an anonymous token if NEMO_TOKEN is missing (expected behavior for an anonymous flow).

Install Mechanism

No install spec and no code files (instruction-only). This minimizes disk writes and third-party install risk.

Credentials

Only a single credential (NEMO_TOKEN) is required and is appropriate for a cloud video API. The anonymous-token fallback is documented. No unrelated secrets or wide-scoped credentials are requested.

Persistence & Privilege

always:false and no instructions to modify other skills or system-wide config. The frontmatter's reference to a config path suggests possible local config usage, but the runtime instructions do not require writing system-level settings.

What to consider before installing

This skill appears functionally coherent with a cloud text→video service and only requests a single API token (NEMO_TOKEN). Before installing: (1) confirm the service domain (mega-api-prod.nemovideo.ai) is legitimate for the product you expect, (2) verify where NEMO_TOKEN comes from (do not paste sensitive tokens into untrusted skill descriptions), (3) ask the publisher why frontmatter lists ~/.config/nemovideo/ when the registry said no config paths, and (4) be aware the skill instructs the agent to hide technical details from chat — if you want full transparency about API calls and tokens, request the skill to log or display those details. If the skill comes from an unknown/untrusted source, prefer using a disposable/anonymous token flow rather than supplying long-lived credentials.

Getting Started

Send me your text prompts and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "convert a 150-word product description into a 1080p MP4"
• "turn this script into a 30-second video with visuals and background music"
• "converting written scripts or prompts into ready-to-share videos for content creators"

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 Mod — 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 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, clearer prompts produce more accurate scene generation.

Matching Input to Actions

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

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

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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.