Music School

create video clips into polished promo videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. music school owners and instructors use it f...

Security Scan

The skill's declared purpose (creating promo videos) matches most of its instructions, but there are a few inconsistencies and behavioral choices — automatic anonymous-token creation, a disparity in declared config-paths, and automatic backend connections/uploads — that warrant caution before installing or using it with sensitive video content.

Purpose & Capability

The skill's name/description (video promo creation) aligns with the APIs and headers described in SKILL.md and the single required env var (NEMO_TOKEN). However, registry metadata provided earlier indicated no required config paths while the SKILL.md frontmatter explicitly lists a config path (~/.config/nemovideo/). That mismatch is an incoherence in metadata vs runtime instructions and should be clarified.

Instruction Scope

SKILL.md instructs the agent to automatically connect to a remote backend, generate an anonymous token if NEMO_TOKEN is not present, upload user-supplied media, stream SSE events, and poll status endpoints. Those operations are coherent with a cloud video-processing service, but they involve automatic network calls and uploading of user files to an external domain (mega-api-prod.nemovideo.ai). The doc also expects the runtime to derive attribution headers from an 'install path' (e.g., ~/.clawhub/) — that implies examining local paths/config which is broader than simply accepting a file and calling an API. The instructions are fairly prescriptive about token handling and state persistence (store session_id) but do not specify where or how session state/token persistence occurs on disk versus memory.

Install Mechanism

This is an instruction-only skill with no install spec and no bundled code to write to disk. That minimizes install-time risk (no external archives or packages are pulled by the skill itself).

Credentials

Only one credential is required (NEMO_TOKEN), which matches the declared primary credential and the service being used. The skill will create an anonymous token if NEMO_TOKEN is missing; that behavior is functionally consistent but means the skill will perform network-auth operations automatically. The SKILL.md also references a config path (~/.config/nemovideo/) that could be used for storage, which wasn't declared elsewhere — this should be clarified.

Persistence & Privilege

always is false (no force-inclusion). The skill tells the agent to 'store the returned session_id for all subsequent requests' and references a config directory in the frontmatter. That suggests some persistence of session state (likely in memory or a skill-scoped config), but the doc does not clearly state whether tokens or session data are written to disk or only kept in-memory. No automatic modification of other skills or agent-wide settings is described.

What to consider before installing

This skill appears to implement what it claims (cloud-based AI video composition) but it will upload your video files to a third-party backend and may create anonymous auth tokens automatically if you don't provide NEMO_TOKEN. Before installing or using it: (1) decide whether you are comfortable uploading student or customer videos to an external service; (2) provide your own NEMO_TOKEN if you want explicit control over credentials rather than allowing the skill to request anonymous tokens; (3) ask the publisher to clarify the config-path and persistence behavior (~/.config/nemovideo/ vs registry metadata) and whether session tokens are ever written to disk; (4) verify the service domain and privacy/retention policy for uploaded media; and (5) require explicit user consent before the skill performs any automatic backend connection or upload. If any of these are unacceptable, do not enable the skill or only use it with non-sensitive test content.

Getting Started

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

Try saying:

• "create a 2-minute recital performance recording into a 1080p MP4"
• "create a promotional video for my music school with student clips and text overlays"
• "creating promotional and enrollment videos for music schools for music school owners and instructors"

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.

1. 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.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. 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.

Music School — Create and Export School Promo Videos

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

Say you have a 2-minute recital performance recording and want to create a promotional video for my music school with student clips and text overlays — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter performance clips under 60 seconds process faster and work best for social media previews.

Matching Input to Actions

User prompts referencing music school, 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 music-school, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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=<id> (get <id> 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 promotional video for my music school with student clips and text overlays" → 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 "create a promotional video for my music school with student clips and text overlays" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 for widest compatibility across school websites and social platforms.