Best To Video Ai

marketers, content creators, educators convert text or script into AI-generated videos using this skill. Accepts TXT, DOCX, PDF, MP4 up to 200MB, renders on...

Security Scan

The skill's declared purpose (text→video rendering) aligns with needing a backend token, but inconsistencies in its metadata and potential for reading local config or using a long-lived bearer token make the package worth closer scrutiny before installing.

Purpose & Capability

The skill claims to convert text into videos and requires a NEMO_TOKEN bearer token for the backend — that is consistent. However, the SKILL.md YAML frontmatter lists a config path (~/.config/nemovideo/) that the registry metadata did not declare; that discrepancy could indicate the skill expects to read local config (e.g., stored tokens) even though the registry says no config paths are required.

Instruction Scope

The runtime instructions are primarily network calls to a single backend (mega-api-prod.nemovideo.ai) and operations needed for upload/session/export. The instructions do not explicitly instruct the agent to read arbitrary user files or unrelated env vars, but they do instruct using NEMO_TOKEN from the environment or obtaining an anonymous token. The presence of an undeclared config path in the frontmatter raises the possibility the agent could also look for local credentials/config, which is not spelled out in the human-facing steps.

Install Mechanism

No install spec or code is included; this is instruction-only, so nothing would be written to disk during install. That lowers risk from arbitrary code install.

Credentials

Only NEMO_TOKEN is declared as a required env var (primary credential), which matches the backend usage. However, the frontmatter's configPaths suggests the skill may access a local config directory (potentially containing persistent tokens or other sensitive data) despite the registry listing none. Accepting a bearer token from environment grants the skill broad access to the backend (including uploads, renders, and account credits/billing), so supplying a personal/global token without limits is potentially risky.

Persistence & Privilege

The skill is not always-enabled and has no install-time persistence. Autonomous invocation (model can call skill) is allowed by default but is not combined here with escalation or system-wide config changes.

What to consider before installing

This skill looks functionally coherent for converting text to video, but there are a few red flags you should consider before installing or exposing credentials: - Source is unknown and there is no homepage or repo; prefer skills from known publishers. - Do NOT export your personal NEMO_TOKEN unless you trust the operator; a bearer token can allow uploads, renders, and billing actions. If you must supply a token, create a limited/test token or account. - The SKILL.md frontmatter references ~/.config/nemovideo/ even though the registry metadata said no config paths — ask the publisher whether the agent will read that directory (it could contain tokens or config). - The skill will upload your files to https://mega-api-prod.nemovideo.ai. Avoid sending sensitive or proprietary content until you confirm the service's privacy/data-retention policies. - Because this is instruction-only, there is no code to inspect; request source code or a public API doc if you need stronger assurance. - If you want to try safely: rely on the advertised anonymous-token flow (ephemeral credits) or create a disposable account/token, and test with non-sensitive content first.

Getting Started

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

Try saying:

• "convert my text or script"
• "export 1080p MP4"
• "convert this article into a short"

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.

Best Text to Video AI — Convert Text into Shareable Videos

Send me your text or script 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 200-word blog post summary, type "convert this article into a short explainer video with visuals and voiceover", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter, focused scripts produce more coherent videos than long unstructured text.

Matching Input to Actions

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

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 best-to-video-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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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 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 → "convert this article into a short explainer video with visuals and voiceover" → 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 "convert this article into a short explainer video with visuals and voiceover" — concrete instructions get better results.

Max file size is 200MB. Stick to TXT, DOCX, PDF, MP4 for the smoothest experience.

Export as MP4 for widest compatibility across social and web platforms.