Ai Text To Youtube

Get YouTube-ready videos ready to post, without touching a single slider. Upload your text or script (TXT, DOCX, PDF, copied text, up to 500MB), say somethin...

Security Scan

The skill's declared requirement (NEMO_TOKEN) and network calls line up with a cloud video service, but a few inconsistencies and opaque instructions warrant caution before installing or providing credentials.

Purpose & Capability

Name/description match what the SKILL.md instructs (convert text to YouTube-ready video). The single required env var (NEMO_TOKEN) is coherent. However, SKILL.md metadata references a config path (~/.config/nemovideo/) not declared in the registry metadata, which is an inconsistency worth calling out (suggests the skill might expect local config or credentials even though the registry did not list them).

Instruction Scope

Runtime instructions are focused on the external NemoVideo API (session creation, upload, SSE streaming, render/export). They instruct the agent to use an env token or obtain an anonymous token from the service — expected for a cloud SaaS integration. Two things to note: (1) the instructions require generating and sending a client UUID and performing network calls to an external domain; (2) the SKILL.md explicitly says to 'keep the technical details out of the chat', which reduces transparency and could hide useful audit information from users. The instructions do not explicitly ask the agent to read arbitrary local files or unrelated environment variables, aside from implicit platform/installation-path detection for an attribution header.

Install Mechanism

Instruction-only skill with no install spec or code to write to disk — lowest-risk install mechanism. No downloads or third-party package installs are requested.

Credentials

Only NEMO_TOKEN is required and is proportional to a cloud video service. The fallback anonymous-token flow is documented (generate client UUID, POST to /api/auth/anonymous-token). The earlier-noted mismatch about a referenced config path (~/.config/nemovideo/) is concerning because it could imply access to local credential/config files that the registry did not declare. The skill also instructs inclusion of attribution headers (X-Skill-Source, X-Skill-Version, X-Skill-Platform) — minor privacy/leakage risk but expected for telemetry/attribution.

Persistence & Privilege

always:false and no install-time persistence are used. The skill operates via transient API sessions/tokens and does not request permanent system-wide privileges or modify other skills. Autonomous invocation is enabled by default (normal) and not in itself flagged here.

Scan Findings in Context

[no-regex-findings] expected: Scanner saw no code files to analyze — this is an instruction-only skill. Absence of findings is expected but not evidence of safety; SKILL.md is the primary surface to review.

What to consider before installing

This skill behaves like a client for nemoVideo (it uses a NEMO_TOKEN or will request a temporary anonymous token from https://mega-api-prod.nemovideo.ai). Before installing or using it: (1) confirm you trust the nemoVideo service and domain; (2) avoid supplying unrelated secrets — only provide a dedicated NEMO_TOKEN for this service; (3) be aware the skill will make network calls and include attribution headers that reveal the skill/version and detected platform; (4) note the SKILL.md tells the agent to hide technical details from chat — that reduces transparency about what it does while running; (5) ask the publisher to clarify the config path reference (~/.config/nemovideo/) and why it differs from the registry metadata, and whether the skill will read any local config files. If you need stronger assurance, request the publisher provide a formal privacy/telemetry statement or a signed manifest explaining what local data (if any) the skill reads.

Getting Started

Got text or script to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "convert a 300-word blog post or article into a 1080p MP4"
• "convert this text into a YouTube-ready video with visuals and voiceover"
• "turning written text or scripts into publishable YouTube videos for YouTubers"

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.

AI Text to YouTube — Convert Text into YouTube Videos

Drop your text or script in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 300-word blog post or article, ask for convert this text into a YouTube-ready video with visuals and voiceover, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter scripts under 500 words produce tighter, more engaging videos.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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 ai-text-to-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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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

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)

Common Workflows

Quick edit: Upload → "convert this text into a YouTube-ready 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 text into a YouTube-ready video with visuals and voiceover" — concrete instructions get better results.

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

Export as MP4 for widest compatibility with YouTube's upload requirements.