Video Maker Intro

create video clips or images into branded intro clip with this skill. Works with MP4, MOV, PNG, JPG files up to 200MB. YouTubers and content creators use it...

Security Scan

The skill largely matches a cloud video-rendering purpose, but several internal inconsistencies and unexpected behaviors (required token vs. auto-generated anonymous token, undeclared config path in frontmatter, unknown source/no homepage, automatic network setup) mean you should review before installing or uploading content.

Purpose & Capability

The name/description (cloud video intro creation) aligns with the endpoints and workflows in SKILL.md (upload, render, export). Requiring a NEMO_TOKEN is coherent for a nemo-video backend. However, the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) that the registry metadata did not list, which is an inconsistency worth noting.

Instruction Scope

Instructions direct the agent to perform network operations (auth, session creation, upload, SSE, polling) and to handle user files — which is expected. They also instruct automatic first-use setup (generate UUID, request anonymous token if no NEMO_TOKEN) and to auto-detect platform from an install path; these imply reading environment and possibly file-system paths. The instructions do not request unrelated credentials, but the auto-setup/network calls mean the agent will contact an external service and may upload user media.

Install Mechanism

There is no install spec and no code files; this instruction-only skill performs network calls at runtime. No downloads or archive extraction are specified.

Credentials

The registry declares NEMO_TOKEN as a required/primary env var (reasonable for a cloud API). But SKILL.md explicitly describes generating an anonymous token if NEMO_TOKEN is absent and then using that token as NEMO_TOKEN — a behavioral inconsistency (required vs. optional). The SKILL.md frontmatter also references a config path (~/.config/nemovideo/) even though required config paths were listed as none, which increases the requested surface without explanation.

Persistence & Privilege

always:false (no forced persistent inclusion). The skill keeps session_id for its own operations but does not request global system changes or other skills' configs. Autonomous invocation is allowed (platform default) but not combined with always:true or broad unrelated credential access.

What to consider before installing

This skill will send your media and API calls to mega-api-prod.nemovideo.ai. Before installing or using it: 1) Verify the service origin and privacy/policies (there's no homepage or publisher info here). 2) Understand that the skill will either use a provided NEMO_TOKEN or obtain an anonymous token automatically — if you don't want the skill to create or use tokens on your behalf, do not grant environment access. 3) The SKILL.md hints at reading a config directory and detecting install paths; if you are uncomfortable, run the skill in an isolated environment or sandbox. 4) Avoid supplying sensitive or private videos until you confirm the vendor/trustworthiness; consider testing with non-sensitive sample files. 5) If you proceed, monitor network requests, and be ready to revoke any token/credential issued by the backend. If you want higher assurance, ask the publisher for a homepage, privacy policy, and API docs, and request that the skill's declared metadata exactly match its runtime behavior (env vars and config paths).

Getting Started

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

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "create a 10-second branded intro with"

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.

Video Maker Intro — Create Branded Video Intros

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

Say you have a logo PNG and a 5-second background clip and want to create a 10-second branded intro with my logo and music — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: keep intros under 10 seconds to hold viewer attention.

Matching Input to Actions

User prompts referencing video maker intro, 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-intro
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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)

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

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.

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

Common Workflows

Quick edit: Upload → "create a 10-second branded intro with my logo and music" → Download MP4. Takes 20-40 seconds 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 "create a 10-second branded intro with my logo and music" — concrete instructions get better results.

Max file size is 200MB. Stick to MP4, MOV, PNG, JPG for the smoothest experience.

Export as MP4 for widest compatibility.