Description

Get branded intro clips ready to post, without touching a single slider. Upload your brand assets, images (PNG, JPG, MP4, MOV, up to 200MB), say something li...

README (SKILL.md)

Getting Started

Ready when you are. Drop your brand assets, images here or describe what you want to make.

Try saying:

"generate a logo PNG and a brand color hex code into a 1080p MP4"
"create a 5-second intro with my logo and a fade-in animation"
"creating short branded intros for YouTube or social media videos for YouTubers, content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer \x3Ctoken>, Content-Type: application/json, and body {"task_name":"project","language":"\x3Cdetected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Intro Maker — Create Branded Video Intros

Name: Intro Maker
Author: vcarolxhberger

Send me your brand assets, images and describe the result you want. The AI intro video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a logo PNG and a brand color hex code, type "create a 5-second intro with my logo and a fade-in animation", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: keep intros under 5 seconds — viewers skip longer ones.

Matching Input to Actions

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

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":"\x3Clang>"}`. 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/\x3Csid>`	POST	Upload a file (multipart) or URL.
`/api/credits/balance/simple`	GET	Check remaining credits (`available`, `frozen`, `total`).
`/api/state/nemo_agent/me/\x3Csid>/latest`	GET	Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
`/api/render/proxy/lambda`	POST	Start export. Body: `{"id":"render_\x3Cts>","sessionId":"\x3Csid>","draft":\x3Cjson>,"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 intro-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).

All requests must include: Authorization: Bearer \x3CNEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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=\x3Cid>` (get `\x3Cid>` 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

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.

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

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 → "create a 5-second intro with my logo and a fade-in animation" → 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 5-second intro with my logo and a fade-in animation" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Usage Guidance

This skill behaves like a thin client for a remote video-rendering service: your uploaded images/video and any prompt text will be sent to https://mega-api-prod.nemovideo.ai and a short-lived token (anonymous or provided via NEMO_TOKEN) will be used. Before installing or using it, consider: 1) Do you trust the NemoVideo domain? Verify the service, privacy policy, and data retention rules — your brand assets and any text you send will be transmitted and processed remotely. 2) The skill may auto-generate and use an anonymous token if NEMO_TOKEN is not set; confirm how and where the agent stores that token (in-memory vs written to disk/environment). 3) Avoid uploading highly sensitive or proprietary media unless you confirm retention/usage terms. 4) The SKILL.md includes a configPath and performs a small install-path check for header attribution — this is not harmful but is a metadata mismatch you may want clarified. If you need stronger guarantees, ask the skill author for a homepage/privacy link and clarification of token storage and data retention policies before use.

Capability Analysis

Type: OpenClaw Skill Name: intro-maker Version: 1.0.0 The intro-maker skill is a legitimate integration for a cloud-based video creation service (nemovideo.ai). It facilitates video rendering by managing sessions, file uploads, and API interactions with its backend. While it automatically provisions an anonymous authentication token and tracks the host platform (e.g., Cursor or ClawHub) for attribution, these actions are consistent with its stated purpose and do not exhibit signs of data exfiltration, malicious execution, or unauthorized access to sensitive local data.

Capability Assessment

✓ Purpose & Capability

The skill claims to create branded video intros and its runtime instructions call a remote video rendering API (mega-api-prod.nemovideo.ai) and require a single service token (NEMO_TOKEN). That credential and the listed endpoints are proportionate to the stated purpose. Minor metadata inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this appears to be a small mismatch in metadata, not a functional mismatch.

ℹ Instruction Scope

Instructions stay within the domain of remote rendering: generate/renew an anonymous token, create a session, upload user media, stream events via SSE, and request exports. The skill will automatically obtain an anonymous token if NEMO_TOKEN is not set and instructs storing session_id for subsequent requests. It also reads the install path to set an X-Skill-Platform header (detects ~/.clawhub/ or ~/.cursor/skills/). Important operational behavior: user media and any prompt text are uploaded to the remote backend; the instructions do not request other unrelated files or credentials. The install-path detection and the small metadata mismatch are scope notes but not concerning by themselves.

✓ Install Mechanism

No install spec or code files are included (instruction-only). Nothing is downloaded or written to disk by an installer as part of the skill package, which reduces installation risk.

✓ Credentials

Only one environment variable is declared (NEMO_TOKEN) and it is directly tied to the remote rendering service. The skill instructs creating an anonymous token when none is present — this is consistent with the need for a service credential. The previously noted configPath in SKILL.md is a minor metadata inconsistency but does not indicate overbroad credential access.

✓ Persistence & Privilege

The skill is not marked always:true and makes no requests to modify other skills or system-wide settings. It stores a session_id for the rendering session, which is normal for a remote session-based API. Autonomous invocation is allowed by default (platform normal) but not combined with other concerning flags.

Version History

v1.0.0

- Initial release of Intro Maker skill. - Instantly create branded 1080p video intros using your own logo, colors, and assets—no design experience needed. - Supports file uploads up to 200MB (PNG, JPG, MP4, MOV, and more). - Easy authentication with free anonymous token; 100 credits included for new users. - Cloud-based editing and rendering—get downloadable MP4s within seconds. - Designed for YouTubers and content creators seeking fast, professional intros.

Metadata

Slug intro-maker

Version 1.0.0

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 1

Frequently Asked Questions

What is Intro Maker?

Get branded intro clips ready to post, without touching a single slider. Upload your brand assets, images (PNG, JPG, MP4, MOV, up to 200MB), say something li... It is an AI Agent Skill for Claude Code / OpenClaw, with 113 downloads so far.

How do I install Intro Maker?

Run "/install intro-maker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Intro Maker free?

Yes, Intro Maker is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Intro Maker support?

Intro Maker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Intro Maker?

It is built and maintained by vcarolxhberger (@vcarolxhberger); the current version is v1.0.0.

More Skills

Intro Maker