Video Maker Ai Youtube

create video clips or images into YouTube-ready MP4 with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers use it for creating polished...

Security Scan

The skill's runtime instructions match its stated purpose (uploading and rendering videos via a Nemo backend), but there are metadata inconsistencies and the skill comes from an unknown source with no homepage — verify the service before giving it credentials or private videos.

Purpose & Capability

The name/description (AI video → YouTube-ready MP4) aligns with the runtime instructions (upload, session, render, export endpoints). However the registry metadata at the top said no config paths while the SKILL.md frontmatter claims a config path (~/.config/nemovideo/). The skill requires one credential (NEMO_TOKEN) which is appropriate for a hosted video API, but the upstream host (mega-api-prod.nemovideo.ai) and owner are not verifiable from the package metadata.

Instruction Scope

SKILL.md limits actions to creating sessions, uploading media, using SSE for edits, polling render status, and returning download URLs. It does not instruct the agent to read unrelated files, other environment variables, or system secrets. It does include logic to mint an anonymous token if NEMO_TOKEN is absent (network POST to an auth endpoint).

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk (nothing is written to disk by an installer).

Credentials

Only a single environment credential (NEMO_TOKEN) is declared as primary, which is reasonable for an API-backed video service. Minor inconsistency: registry summary indicated 'Required config paths: none' while SKILL.md frontmatter lists a config path (~/.config/nemovideo/). No other unrelated secrets are requested.

Persistence & Privilege

always is false and the skill does not request persistent system-wide privileges or modify other skills. Agent autonomous invocation is allowed (platform default) but not by itself a concern here.

What to consider before installing

This skill appears to do what it says (upload video, create renders on a Nemo backend), but exercise caution before installing or providing credentials: 1) The package has no homepage and an unverified owner — confirm the legitimacy of mega-api-prod.nemovideo.ai and the 'NEMO_TOKEN' issuer before supplying real API keys. 2) The SKILL.md allows the skill to obtain an anonymous token automatically if no NEMO_TOKEN is present — this means it will call an external auth endpoint and then send your uploaded media to that backend. Do NOT upload sensitive or private video/audio unless you trust the service and have reviewed its privacy/terms. 3) There's a metadata mismatch about config paths; treat this as a minor red flag and ask the author to clarify. If you need higher assurance, request the skill's source code or an official homepage/documentation and verify the API host and token issuer before use.

Getting Started

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

Try saying:

• "create a 2-minute screen recording or five product images into a 1080p MP4"
• "turn my clips into a YouTube video with intro, transitions, and captions"
• "creating polished YouTube videos from raw clips using AI 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.

Video Maker AI YouTube — Create and Export YouTube Videos

Drop your video clips or images 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 2-minute screen recording or five product images, ask for turn my clips into a YouTube video with intro, transitions, and captions, 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 source clips under 3 minutes process significantly faster and give the AI more precise control over pacing.

Matching Input to Actions

User prompts referencing video maker ai 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.

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

Header	Value
X-Skill-Source	video-maker-ai-youtube
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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 my clips into a YouTube video with intro, transitions, and captions" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 with H.264 codec for widest YouTube compatibility and smaller file size.

Common Workflows

Quick edit: Upload → "turn my clips into a YouTube video with intro, transitions, 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.