Youtube Video Maker

Get polished YouTube videos ready to post, without touching a single slider. Upload your video clips or images (MP4, MOV, AVI, WebM, up to 500MB), say someth...

Security Scan

The skill's declared purpose (cloud video creation) matches its instructions and required credential (NEMO_TOKEN); it uploads user media to nemovideo.ai and uses that token for API calls — nothing strongly mismatched, but there are a few minor inconsistencies and privacy considerations to be aware of.

Purpose & Capability

The skill claims to produce YouTube-ready videos and the runtime instructions only call a video-processing API (https://mega-api-prod.nemovideo.ai) and related endpoints. Requesting a single service token (NEMO_TOKEN) is proportional to that purpose.

Instruction Scope

Instructions focus on creating sessions, uploading media, streaming SSE, and exporting renders to a download URL — all consistent with a cloud video service. They explicitly direct user-supplied files to an external API (expected for this use). The doc also instructs deriving headers from the skill frontmatter and detecting the agent's install path to set X-Skill-Platform, which implies reading certain local paths; this is a small scope creep (checking paths in the home directory) but not grossly out-of-scope.

Install Mechanism

No install spec or third-party downloads exist; the skill is instruction-only, so nothing is written to disk by an installer — this is low risk.

Credentials

Only NEMO_TOKEN is declared as required and is appropriate for authenticating to the service. However, the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata listed none; that mismatch should be resolved. Also, anonymous-token flow creates a token client-side which the agent will store for requests — consider how/where that token is persisted and whether the token is treated as sensitive.

Persistence & Privilege

always is false and the skill does not request system-wide privileges. The skill may detect presence of install directories (~/.clawhub, ~/.cursor/skills/) to populate an X-Skill-Platform header, which requires only lightweight path checks; this is not a high privilege request.

Assessment

Before installing, consider the following: - This skill uploads whatever media you provide to an external service (mega-api-prod.nemovideo.ai). Do not upload private or sensitive footage you wouldn't want sent to a third party. - The only required secret is NEMO_TOKEN. If you don't have one the skill will create an anonymous token via the service's anonymous-token endpoint; that token grants credits and is bearer auth for future requests — treat it as sensitive and confirm where the agent will store it (ephemeral vs persistent). - There is a minor metadata inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shows no required config paths. Ask the publisher which (if any) local paths the skill will read or write. - The skill may check for certain install directories to set an X-Skill-Platform header (it may probe ~/.clawhub or ~/.cursor/skills/). If you are uncomfortable with any local path checks, ask for clarification or a version that skips platform detection. - The source and homepage are unknown; if you rely on this for important or sensitive work, verify the service operator (nemovideo.ai) and their privacy/retention policies first. If you want higher assurance, request the publisher to: (1) confirm whether the skill ever persists NEMO_TOKEN to disk and where, (2) remove or justify the config path in the frontmatter, and (3) provide a homepage or documentation and a trusted owner identity.

Getting Started

Share your video clips or images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "combine my clips, add titles, and"

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 Video Maker — 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 three 30-second clips and a background music file, ask for combine my clips, add titles, and export for YouTube in 1080p, 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 2 minutes process significantly faster.

Matching Input to Actions

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

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is youtube-video-maker, 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).

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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)

Common Workflows

Quick edit: Upload → "combine my clips, add titles, and export for YouTube in 1080p" → 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 "combine my clips, add titles, and export for YouTube in 1080p" — 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 the best balance of quality and file size on YouTube.