Text To Video Ai App

Skip the learning curve of professional editing software. Describe what you want — turn this script into a 30-second video with visuals and background music...

Security Scan

The skill behaves like a legitimate text→video frontend (it will send files/text to an external nemovideo.ai service using a NEMO_TOKEN) but there are metadata/instruction inconsistencies and a few scope/privacy concerns you should review before installing.

Purpose & Capability

The skill's stated purpose (convert text/scripts to videos) matches the runtime instructions that call a nemovideo.ai API and accept uploads. However the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — that mismatch is unexplained. The skill also requires detecting an install path to set an attribution header, which implies the agent may read local path information. These details are not clearly justified by the short description.

Instruction Scope

The instructions tell the agent to upload user text/files (up to 200MB) and send them to https://mega-api-prod.nemovideo.ai, obtain or use a Bearer token, open SSE streams, and poll export endpoints. That is coherent for a cloud rendering service, but the instructions also (a) derive an X-Skill-Platform header from the install path (which requires filesystem inspection) and (b) do not explicitly limit what agent context is sent — conversation context or other environment values could be included unless implementation is careful. The agent is also instructed to auto-acquire an anonymous token if NEMO_TOKEN is absent, which is fine but means network calls will be made automatically.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, which minimizes install-time risk (nothing is downloaded or written by the skill bundle itself).

Credentials

Only one credential is declared (NEMO_TOKEN) and that aligns with a hosted API service. The SKILL.md flow will auto-request an anonymous token if none is present. The remaining concern is that metadata references a config path (~/.config/nemovideo/) and the agent may read install paths to build headers — both could expose local paths or config contents; the registry did not declare these config paths, so the reason for them is unclear.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform persistence. Autonomous invocation is allowed (platform default) but that alone is not a new risk given the skill's network behaviour.

What to consider before installing

This skill appears to implement a cloud text→video workflow and will send user text and uploaded files to an external API (mega-api-prod.nemovideo.ai). Before installing: (1) Confirm you trust that external service and its privacy policy — do not upload sensitive data. (2) Ask the author to clarify the configPaths vs registry metadata mismatch (why ~/.config/nemovideo/ is referenced). (3) If you do not want the agent to reveal local install paths or extra context, request that headers be fixed to not depend on filesystem detection. (4) Consider using an anonymous/throwaway NEMO_TOKEN for testing, and review logs to confirm only intended data is transmitted. (5) Because source/homepage are unknown, treat this as unverified third-party software and test with non-sensitive files first.

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

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"
• "generating videos from written scripts or text prompts for marketers, content creators, social media managers"

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 AI App — 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 150-word product description, ask for turn this script 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 scripts produce more accurate and polished video output.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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)

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

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 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 across all platforms and devices.

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.