Text To Video Making Ai

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

Security Scan

The skill's behavior mostly matches a cloud-based text->video service (it only needs a NEMO_TOKEN and talks to nemovideo.ai), but there are small inconsistencies and privacy-relevant behaviors (automatic anonymous-token creation, implicit upload of user content, and a mismatched config-path declaration) that you should understand before installing.

Purpose & Capability

Name/description match the instructions: it contacts a cloud video backend (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN. That credential and the APIs described are coherent with a text-to-video service. However, the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) while the registry metadata reported earlier said no required config paths — this mismatch is an inconsistency you should confirm with the author.

Instruction Scope

Instructions are explicit about creating sessions, using SSE, uploading user files (multipart or URLs), and polling render endpoints. The skill will automatically POST to an anonymous-token endpoint to mint a NEMO_TOKEN when one isn't present — meaning it will reach out to the external service and create a transient credential without an explicit interactive consent step. The runtime directions do not ask for unrelated files or extra system secrets, but they do direct user-supplied files and any text prompts to an external service (uploads up to 500MB). This is expected for the stated purpose but has clear privacy implications.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. All operations are described as remote API calls; nothing is written to disk by an installer as part of the skill itself. The only minor oddity is deriving X-Skill-Platform from an install path (reading path strings) — harmless but unnecessary.

Credentials

Only NEMO_TOKEN is declared as required (primary credential) which matches the described API. The skill's fallback to automatically obtain an anonymous NEMO_TOKEN if none is present is notable: it reduces friction but also means the skill will obtain and use credentials on your behalf. No other unrelated secrets are requested.

Persistence & Privilege

The skill does not request always:true or other elevated persistent privileges. It keeps a session_id for its own operations (normal) and does not instruct modification of other skills or system-wide settings.

What to consider before installing

This skill appears to implement a standard cloud text→video flow, but review these before installing: - Confirm you trust the external service (mega-api-prod.nemovideo.ai / NemoVideo). Uploaded text/files and generated videos are sent to that service. - The skill will create an anonymous NEMO_TOKEN for you if none is provided. If you prefer to control credentials, set your own NEMO_TOKEN instead of relying on the anonymous flow. - There is an inconsistency: the SKILL.md declares a config path (~/.config/nemovideo/) while the registry metadata showed no required config paths. Ask the publisher why a local config path is needed and whether the skill will read or write files there. - Be cautious about uploading sensitive content (proprietary text, customer data, PII) since the processing occurs on the vendor's cloud. If you cannot verify the service's privacy policy or the skill's publisher, treat the skill as untrusted for sensitive data. If you decide to proceed, prefer providing your own NEMO_TOKEN (from an account you control) and avoid uploading confidential files.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "turn this blog intro 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 Making AI — Turn 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 blog intro 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 text prompts produce more accurate and focused video output.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is text-to-video-making-ai, 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.

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.

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)

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

Common Workflows

Quick edit: Upload → "turn this blog intro 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 blog intro into a 30-second video with visuals and background 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 across social and web platforms.