Demo Clip Maker

create raw footage into polished demo clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. marketers use it for generating short product...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video-processing service: it needs a service token and sends user videos to nemovideo.ai for processing; there are no obvious requests for unrelated credentials or invasive local access.

Purpose & Capability

The name/description (create demo clips) match the declared requirement (NEMO_TOKEN) and the SKILL.md endpoints (nemovideo.ai). Requiring a single service token is proportionate for a cloud-rendering workflow.

Instruction Scope

Instructions direct the agent to obtain/use NEMO_TOKEN, create sessions, upload user media, use SSE for edits, and poll export status — all aligned with video processing. The skill explicitly instructs reading its own YAML frontmatter and detecting install path (to set X-Skill-Platform), which requires access to the skill file and possibly probing common install paths in the user home directory; this is plausible for attribution but is broader filesystem access than strictly necessary.

Install Mechanism

No install spec or code is present (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is requested (primary credential), which fits a third-party API. The SKILL.md also explains how to obtain an anonymous token via the service API if NEMO_TOKEN is not provided — reasonable but means the skill can self-provision short-lived credentials without user-supplied secrets. There is a minor metadata discrepancy: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths.

Persistence & Privilege

The skill is not marked always:true and doesn't request persistent system privileges or to modify other skills. Autonomous invocation is allowed (platform default) but not combined with other concerning flags.

Assessment

This skill appears coherent for a cloud video-processing service, but consider these before enabling it: (1) Using the skill uploads your video files to https://mega-api-prod.nemovideo.ai — do not send sensitive or private footage unless you trust that domain and its privacy policy. (2) The skill can generate an anonymous NEMO_TOKEN itself, so it will call the external auth endpoint automatically if you don't provide a token. (3) The runtime asks the agent to read the skill's frontmatter and check common install paths (~/.clawhub, ~/.cursor, etc.), which requires limited filesystem access; ensure your environment policy allows this. (4) The package source and homepage are unknown and the owner ID is opaque — if you need stronger assurance, ask the publisher for a homepage, privacy policy, or official documentation and confirm the nemovideo.ai domain is legitimate. (5) If you have compliance or sensitive-data concerns, disable the skill or inspect outbound network activity / request logs before uploading real content.

Getting Started

Share your raw footage and I'll get started on AI demo clip creation. Or just tell me what you're thinking.

Try saying:

• "create my raw footage"
• "export 1080p MP4"
• "trim the best moments and compile"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Demo Clip Maker — Create and Export Demo Clips

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

Say you have a 3-minute product walkthrough recording and want to trim the best moments and compile them into a 60-second demo clip — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: keeping source footage under 2 minutes produces tighter, more focused demo clips.

Matching Input to Actions

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

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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: demo-clip-maker
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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)

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the best moments and compile them into a 60-second demo clip" — 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 websites and presentations.

Common Workflows

Quick edit: Upload → "trim the best moments and compile them into a 60-second demo clip" → 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.