Text To Best

Get polished video clips ready to post, without touching a single slider. Upload your text prompt (TXT, DOCX, PDF, plain text, up to 500MB), say something li...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud text→video service: it asks for a single service token, calls APIs on a nemo-video domain, and has no install or unrelated credentials — aside from a small metadata mismatch about a config path.

Purpose & Capability

The skill is a text→video generator and only requests a NEMO_TOKEN (the service token) and references a nemovideo config path in the SKILL.md frontmatter. That matches its stated purpose. Minor inconsistency: the registry summary shows no required config paths, while the SKILL.md metadata lists ~/.config/nemovideo/ — this is likely a bookkeeping mismatch but worth noting.

Instruction Scope

Runtime instructions stay within the video generation workflow: create/refresh a session, send SSE messages, upload user files (multipart or URL), query credits/state, and poll export results. The agent is instructed to include the service token in Authorization headers and to avoid printing tokens/raw JSON. No instructions ask the agent to read unrelated system files or other credentials.

Install Mechanism

No install steps or downloaded code are present (instruction-only). That minimizes on-disk risk.

Credentials

Only NEMO_TOKEN is declared as required. The SKILL.md also describes creating an anonymous token via the service if no token is present, so a preexisting secret is optional. The only small surprise is the SKILL.md metadata claiming a config path (~/.config/nemovideo/) despite the registry metadata reporting none; this is likely non-critical but inconsistent.

Persistence & Privilege

The skill does not request always: true and does not modify other skills. It asks the agent to store session_id for job polling, which is normal for a long-running cloud render workflow.

Assessment

This skill appears to do what it says: it uploads your text and any files you provide to nemo's cloud API and returns rendered video URLs. Before installing or using it, consider: (1) NEMO_TOKEN (or an anonymous token) grants the skill access to the nemo service and any associated account credits — treat it like a credential. (2) Uploaded files and prompts are sent to https://mega-api-prod.nemovideo.ai — don't send sensitive private data unless you trust that service. (3) The SKILL.md and registry metadata disagree about a config path (~/.config/nemovideo/) — this is likely harmless but you may want to confirm what local files (if any) the skill will read. (4) No other external endpoints or unrelated credentials are requested. If you need stronger assurance, ask the publisher for a privacy policy or inspect network logs during a test run.

Getting Started

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

Try saying:

• "convert my text prompt"
• "export 1080p MP4"
• "turn this product description into a"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Text to Video — Convert Text Into Shareable Videos

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

A quick example: upload a 200-word product description or script, type "turn this product description into a 30-second promo video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter, clearer text prompts produce more accurate and focused video outputs.

Matching Input to Actions

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

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.

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)

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 product description into a 30-second promo video" → 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 product description into a 30-second promo video" — concrete instructions get better results.

Max file size is 500MB. Stick to TXT, DOCX, PDF, plain text for the smoothest experience.

Export as MP4 for widest compatibility across all platforms and devices.