Youtube Text To

convert text script into text-based videos with this skill. Works with TXT, DOCX, PDF, SRT files up to 200MB. YouTubers use it for converting written text in...

Security Scan

The skill's functionality and required credential (NEMO_TOKEN) match its stated purpose, but there are a few inconsistencies and privacy/transfer risks (unknown source, file uploads to an external API, and a metadata mismatch) you should understand before installing.

Purpose & Capability

The skill claims to convert text into server-rendered videos and the SKILL.md describes a cloud render pipeline, upload endpoints, and a single required credential (NEMO_TOKEN). Those requirements are proportionate to the stated purpose.

Instruction Scope

The instructions explicitly tell the agent to upload user-provided files (up to 200MB) and send content to https://mega-api-prod.nemovideo.ai. That is expected for a cloud rendering service but is a privacy/egress concern: user files and text will be transmitted to an external service. The SKILL.md also instructs saving and reusing session tokens and polling SSE endpoints; it does not ask the agent to read unrelated system files, but it will use any NEMO_TOKEN present in the environment.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is a low-risk install surface, but runtime network calls are how the skill operates.

Credentials

The only declared required environment variable is NEMO_TOKEN (primary credential), which is proportionate. However: SKILL.md metadata references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is an inconsistency worth asking the publisher to clarify. Also, the agent will reuse any existing NEMO_TOKEN in the environment, which may cause it to act under an existing account if present.

Persistence & Privilege

always:false and normal model invocation settings. The skill does not request permanent system-wide presence or modify other skills. It does instruct saving session tokens for use across requests, which is expected behavior for a remote API client.

What to consider before installing

This skill will upload your text and any files you provide to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN (it will use any such token already in your environment or can request an anonymous token). Before installing or invoking it: 1) confirm you trust the remote service and its privacy policy (you'll be sending content off your machine); 2) be aware that if you already have a NEMO_TOKEN env var it will be used (so the skill may act under an existing account); 3) ask the publisher to explain the metadata mismatch (SKILL.md references ~/.config/nemovideo/ but registry metadata lists no config paths); and 4) avoid uploading sensitive or confidential data to an unknown/unstaffed service. If you need stronger assurance, request source code, a homepage/privacy policy, or a vendor identity before using the skill.

Getting Started

Ready when you are. Drop your text script here or describe what you want to make.

Try saying:

• "convert a 200-word blog post or article into a 1080p MP4"
• "convert this text into a YouTube video with voiceover and captions"
• "converting written text into YouTube-ready videos for YouTubers"

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.

YouTube Text To Video — Convert Text Into YouTube Videos

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

Worth noting: shorter scripts under 300 words produce tighter, more engaging videos.

Matching Input to Actions

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

Common Workflows

Quick edit: Upload → "convert this text into a YouTube video with voiceover and captions" → 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 text into a YouTube video with voiceover and captions" — 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.