Maker Intro

Turn a logo PNG and a tagline into 1080p branded intro video just by typing what you need. Whether it's creating short branded intro clips for YouTube or soc...

Security Scan

The skill's behavior mostly matches a cloud-based video-renderer, but there are inconsistencies and minor privacy/scope concerns (token handling, filesystem/installation-path detection) that you should understand before installing.

Purpose & Capability

The skill claims to create branded intro videos via a cloud backend and its HTTP endpoints and upload flow match that purpose. However the registry metadata marks NEMO_TOKEN as a required environment variable while the SKILL.md explicitly contains steps to obtain an anonymous token if NEMO_TOKEN is not present — this mismatch between declared requirements and runtime behavior is inconsistent and should be clarified.

Instruction Scope

Runtime instructions tell the agent to make many HTTP calls (auth, session creation, SSE, upload, render/export) and to upload user-supplied files to https://mega-api-prod.nemovideo.ai, which is expected for this service. But the skill also asks the agent to detect install paths (~/.clawhub, ~/.cursor/skills/) and references a local config path (~/.config/nemovideo/). Detecting install paths or reading those filesystem locations is beyond simple upload/render behavior and could leak local environment metadata; the SKILL.md does not clearly justify or limit that filesystem access.

Install Mechanism

Instruction-only skill with no install spec or downloadable code. No code is written to disk by the skill bundle itself — this is the lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is declared as a required env var and makes sense for a cloud API. But declaring it as required while providing an anonymous-token acquisition flow is contradictory. No other unrelated credentials are requested. The metadata's configPaths entry (~/.config/nemovideo/) implies local config storage but the instructions don't clearly explain what is stored there.

Persistence & Privilege

Skill does not request 'always: true' and does not ask to modify other skills or global settings. It does instruct keeping a session_id for the session lifecycle and references a local config path for config — that is reasonable for session state but you should confirm whether tokens/session IDs are persisted to disk and where.

What to consider before installing

This skill appears to genuinely implement a cloud-based intro-video workflow, but there are a few things to check before installing or using it: 1) Clarify the NEMO_TOKEN requirement — the manifest says it's required but the instructions obtain an anonymous token if none is supplied; ask the author why the env var is required. 2) Be aware all uploaded assets (logos, audio, etc.) are sent to https://mega-api-prod.nemovideo.ai — don't upload sensitive content unless you trust the service and reviewed its privacy policy. 3) The skill asks the agent to detect install paths and references ~/.config/nemovideo/ — confirm what local files (if any) it will read or write and whether session tokens are stored on disk. 4) If you need tighter control, prefer providing a pre-provisioned NEMO_TOKEN (if you trust the service) and avoid sending any files you wouldn't permit on an external service. 5) Because this is an instruction-only skill with no author homepage or repo listed, request provenance (who operates mega-api-prod.nemovideo.ai, a privacy policy, or a homepage) before trusting it. If you can't verify those things, treat this skill as potentially privacy-invasive and avoid installing or uploading confidential assets.

Getting Started

Share your brand assets, text and I'll get started on AI intro video creation. Or just tell me what you're thinking.

Try saying:

• "create my brand assets, text"
• "export 1080p MP4"
• "create a 10-second intro video 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.

Maker Intro — Create Branded Intro Videos

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

Here's a typical use: you send a a logo PNG and a tagline, ask for create a 10-second intro video with my logo and brand name, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — keep your intro under 10 seconds to hold viewer attention.

Matching Input to Actions

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

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 maker-intro, 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

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.

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 → "create a 10-second intro video with my logo and brand name" → Download MP4. Takes 30-60 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 intro video with my logo and brand name" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.