Text To Video Maker 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 requests and runtime instructions are consistent with a cloud text→video service: it needs a NEMO_TOKEN (or will obtain an anonymous token), talks to nemovideo.ai endpoints, and does not ask for unrelated secrets or installs code locally.

Purpose & Capability

Name/description match the behavior: remote GPU rendering, upload endpoints, session creation, rendering/export and credit checks. Requiring NEMO_TOKEN as the primary credential is expected for a hosted video API.

Instruction Scope

SKILL.md explicitly instructs the agent to POST to nemovideo.ai auth, session, upload, render and SSE endpoints and to upload user files (up to 500MB). This is appropriate for a cloud video service, but it does transmit user content to an external service — which is expected but important for privacy. The doc also asks the agent to detect an install path to set an X-Skill-Platform header (reads install location); that's minor but worth noting.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. No downloads, archives, or third-party package installs are requested.

Credentials

Only NEMO_TOKEN is required (primaryEnv). The skill can create an anonymous token if NEMO_TOKEN is absent, which is coherent. Minor inconsistency: SKILL.md metadata mentions configPaths (~/.config/nemovideo/) while the registry metadata lists no required config paths; this is likely harmless but inconsistent.

Persistence & Privilege

always:false and no install-time persistence or modification of other skills. The skill can be invoked autonomously (platform default), which is normal for skills.

Assessment

This skill will send any text and uploaded files you provide to the nemovideo.ai backend for processing. Only install/use it if you trust that service and are comfortable uploading the (possibly sensitive) content you plan to convert. Make sure any NEMO_TOKEN you provide comes from a trusted source; if you don't set one the skill will request an anonymous token from the service (100 free credits, short expiry). Note the small metadata inconsistency (a config path is mentioned in SKILL.md but not declared in registry) — not a functional red flag but worth being aware of. If privacy is a concern, avoid uploading confidential material or verify the provider's privacy/retention policy first.

Getting Started

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

Try saying:

• "convert my written 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 Maker AI — Convert Text into Shareable Videos

Send me your written text prompts and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 150-word product description paragraph, type "turn this blog intro into a 30-second video with visuals and background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter text inputs under 100 words tend to produce tighter, more focused videos.

Matching Input to Actions

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

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.

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

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

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.

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)

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 platforms and websites.

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.