Colab Text To Video

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

Security Scan

The skill's instructions and required credential (NEMO_TOKEN) are consistent with a text→video cloud rendering service, but it will upload user content to a third‑party API and there is a small metadata mismatch you should review before installing.

Purpose & Capability

The name/description match the runtime instructions: the skill calls a nemo-video backend to render videos and uses a single API token (NEMO_TOKEN). Minor incoherence: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shows no required config paths — this mismatch should be clarified but does not by itself break purpose alignment.

Instruction Scope

The SKILL.md explicitly instructs the agent to create sessions, stream SSE for editing, upload user files (TXT/DOCX/PDF up to 500MB), and poll for render results at mega-api-prod.nemovideo.ai. All of that is within the stated purpose (cloud render pipeline). Important privacy note: user prompts and uploaded files are transmitted to the external service; the skill also instructs the agent to hide technical details from the user.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. Low install risk.

Credentials

Only one credential is required (NEMO_TOKEN), which is proportional for a cloud API. The skill also supports obtaining an anonymous token by POSTing to the provider's auth endpoint. Clarify whether reading the optional local config path (~/.config/nemovideo/) is required — frontmatter mentions it but the package metadata did not declare it. Keep in mind NEMO_TOKEN will be sent as Authorization: Bearer to the external service.

Persistence & Privilege

The skill does not request always:true and is only user-invocable by default. It does not ask to modify other skills or system-wide config. Agent autonomous invocation is allowed by platform default (no extra privilege requested).

Assessment

This skill appears to be what it says: it uploads your prompts and any files you provide to the nemovideo backend and uses an API token (NEMO_TOKEN). Before installing, confirm you trust the destination (mega-api-prod.nemovideo.ai) with the content you will upload and with any NEMO_TOKEN you provide. Ask the publisher to clarify the configPath discrepancy (~/.config/nemovideo/ in SKILL.md vs none in registry) if you care about local config access. If you don’t want to supply a permanent token, you can rely on the anonymous-token flow (limited credits), but be aware that prompts and files will still be sent to the third‑party service. If the content is sensitive, do not upload it to this skill.

Getting Started

Send me your text prompts and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "convert a 3-sentence product description into a 1080p MP4"
• "turn this text into a 30-second video with visuals and background music"
• "generating videos from written scripts or descriptions for content creators, marketers, students"

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.

Colab Text to Video — Convert Text Into Video Clips

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 3-sentence product description and want to turn this text into a 30-second video with visuals and background music — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

Tip: shorter, clearer text prompts produce more accurate and coherent video output.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	colab-text-to-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this text 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, plain text for the smoothest experience.

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "turn this text into a 30-second video with visuals and background music" → Download MP4. Takes 1-3 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.