Text To Video For Youtube

Skip the learning curve of professional editing software. Describe what you want — turn this script into a YouTube video with visuals and voiceover — and get...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based text→video service: it needs a single service token, talks to nemovideo.ai endpoints, and will upload user content for remote rendering.

Purpose & Capability

The skill is a text-to-video frontend that calls a cloud rendering API. Requiring a NEMO_TOKEN and calling https://mega-api-prod.nemovideo.ai endpoints is coherent with the stated purpose. One minor inconsistency: the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata earlier listed no required config paths.

Instruction Scope

The instructions explicitly direct the agent to upload user scripts/files (up to 200MB) and to call SSE and REST endpoints on nemovideo.ai — this is expected for remote rendering, but it means user content (scripts/media) is transmitted to a third-party cloud. The skill also instructs creating an anonymous token if NEMO_TOKEN is absent. No instructions ask the agent to read unrelated local files or secrets, but users should be aware of the content upload/exfiltration-by-design risk.

Install Mechanism

Instruction-only skill with no install step and no code files; lowest install risk. Nothing is downloaded or written as part of an install spec.

Credentials

Only one credential is required (NEMO_TOKEN), which is proportional to a cloud video service. The SKILL.md will auto-obtain an anonymous token via the provider's anonymous-token endpoint if NEMO_TOKEN is not present (100 free credits, 7-day expiry). The frontmatter's config path (~/.config/nemovideo/) suggests the agent could look for local provider config — a minor mismatch with registry metadata that said no config paths; this could allow the agent to read that specific config file if present.

Persistence & Privilege

The skill is not marked always:true and has no install persistence. It does not request elevated platform privileges. Autonomous invocation is allowed but is the platform default and not, by itself, a red flag.

Assessment

This skill routes scripts and uploaded media to nemovideo.ai for cloud rendering and requires a NEMO_TOKEN (or will create an anonymous token for you). If you install it, expect your text and any uploaded files to be sent to that third-party service. Before installing, confirm you trust the nemovideo.ai endpoint and its privacy/retention policies, avoid uploading sensitive or proprietary content, and consider providing your own NEMO_TOKEN rather than allowing automatic anonymous token creation. Note the minor metadata mismatch about a local config path (~/.config/nemovideo/) — the agent may look there for credentials if present.

Getting Started

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

Try saying:

• "convert a 200-word blog post intro into a 1080p MP4"
• "turn this script into a YouTube video with visuals and voiceover"
• "generating YouTube videos from written scripts or text for YouTubers"

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 for YouTube — Convert Scripts into YouTube Videos

This tool takes your text script and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 200-word blog post intro and want to turn this script into a YouTube video with visuals and voiceover — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 300 words produce faster and more focused videos.

Matching Input to Actions

User prompts referencing text to video for youtube, 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 text-to-video-for-youtube, 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)

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this script into a YouTube video with visuals and voiceover" — concrete instructions get better results.

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

Export as MP4 for widest compatibility with YouTube uploads.

Common Workflows

Quick edit: Upload → "turn this script into a YouTube 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.