Maker Intro Free

Turn a logo image and a tagline text into 1080p branded intro videos just by typing what you need. Whether it's creating free intro clips for YouTube or soci...

Security Scan

The skill's declared purpose (create branded intro videos) mostly matches what it does, but there are small incoherences around declared config paths and instructions that imply reading local install/config paths — things the skill doesn't clearly need — so review before installing.

Purpose & Capability

The name/description (make intro videos) aligns with the runtime instructions: it uploads user media, creates a session, posts render jobs, and returns download URLs from nemo's API. The single required environment variable (NEMO_TOKEN) and the listed endpoints are consistent with a cloud-rendering integration.

Instruction Scope

Most runtime steps stay on-purpose (upload files, create session, stream SSE, start render). However the instructions mention detecting the agent's install path to set X-Skill-Platform and reference config path(s) in the frontmatter. Detecting install/config paths implies inspecting local filesystem state that is not strictly necessary for video rendering and broadens scope of access. Also the frontmatter includes a configPaths entry (~/.config/nemovideo/) even though the registry metadata said no config paths — this inconsistency is unexplained.

Install Mechanism

No install spec and no code files — instruction-only. This is lower-risk because nothing is downloaded or written by an installer.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is appropriate for a cloud service. But the SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) and the instructions imply reading install paths to set headers; that increases privilege scope beyond the single token and is not justified by the stated functionality. Confirm whether the skill actually needs to read local config files before providing any credentials.

Persistence & Privilege

Skill does not request always:true and has no install-time persistence. Autonomous invocation is allowed (platform default) but not combined with elevated privileges or persistent presence.

What to consider before installing

This skill appears to legitimately call a nemo video API to upload media, create sessions, stream progress, and return a download URL — that part is coherent. Things to check before installing or using it: 1) Be careful which token you provide: NEMO_TOKEN will be sent to https://mega-api-prod.nemovideo.ai as a Bearer token, so only use a token you intend to share with that service (avoid using unrelated or high-privilege tokens). 2) Ask the publisher (or inspect a code implementation) whether the skill actually reads ~/.config/nemovideo/ or probes install paths; if it does, ask why that local data is needed. 3) If you prefer more isolation, use the skill with no NEMO_TOKEN so it falls back to the anonymous token flow, or avoid uploading sensitive media. 4) The skill is instruction-only (no installs), which reduces risk, but the metadata inconsistency (registry vs SKILL.md configPaths) should be clarified before trusting it with credentials or private files.

Getting Started

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

Try saying:

• "create a logo image and a tagline text into a 1080p MP4"
• "create a free intro video with my logo and brand name"
• "creating free intro clips for YouTube or social media channels 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.

Maker Intro Free — Create Free Branded Intro Videos

Drop your images or clips 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 image and a tagline text, ask for create a free 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 5 seconds for better viewer retention.

Matching Input to Actions

User prompts referencing maker intro free, 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":"<lang>"}. 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/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"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 maker-intro-free, 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).

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

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

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.

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

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 free 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 free intro video with my logo and brand name" — 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.