Video Clip Maker

Get polished video clips ready to post, without touching a single slider. Upload your raw footage (MP4, MOV, AVI, WebM, up to 500MB), say something like "tri...

Security Scan

The skill's behavior (uploading user video files to a remote API and creating/using session tokens) is coherent with its stated purpose, but there are small inconsistencies and privacy/transparency concerns you should understand before installing.

Purpose & Capability

The name/description (remote video clip editing) matches the actions described (upload, SSE-based editing, render/export). Requiring a single API token (NEMO_TOKEN) is appropriate. However, metadata in the SKILL.md references a config path (~/.config/nemovideo/) while registry metadata lists no required config paths — this mismatch should be clarified.

Instruction Scope

Runtime instructions direct the agent to upload user-provided video files to an external service (mega-api-prod.nemovideo.ai), create anonymous tokens when none are present, open sessions, stream SSE, poll renders, and include attribution headers. Those actions are expected for a cloud-based editor, but the instructions also explicitly tell the agent to 'keep the technical details out of the chat' (reduces transparency) and to detect an install path to set a header (requires reading local paths). The skill will therefore read an env var, potentially read local install/config paths, and transmit user files and session tokens to a third-party API — a notable privacy/network activity that users should be aware of.

Install Mechanism

Instruction-only skill with no install spec and no bundled code — nothing is written to disk by an installer. This is the lowest install risk.

Credentials

Only one environment variable (NEMO_TOKEN) is required, which is appropriate for an API-backed service. The SKILL.md describes creating and using an anonymous token if none exists, so the agent may create and use credentials at runtime. The SKILL.md metadata references a config path (~/.config/nemovideo/) that could be used to persist tokens; the registry listing omitted required config paths — this inconsistency should be clarified. No other unrelated credentials are requested.

Persistence & Privilege

The skill does not request always:true and doesn't modify other skills. It can be invoked autonomously (platform default), which combined with network access increases blast radius but is not unusual for a networked skill.

What to consider before installing

This skill will send any video you upload and session tokens to a third‑party API (mega-api-prod.nemovideo.ai) for server-side editing — that is how it works but it has privacy implications. Before installing or using it, confirm: (1) you trust the Nemo service and its privacy/retention policy (will uploads be stored/retained?), (2) you are comfortable with the skill creating/using anonymous tokens (it may persist them under ~/.config/nemovideo/ per the SKILL.md metadata), (3) you do not expose a more privileged token in NEMO_TOKEN (use an ephemeral or least-privilege token), and (4) you are okay with the agent reading the skill install path or config location to populate headers. Also note the skill instructs the agent to hide technical details from users — if you need auditability or transparency of network activity, ask the owner for a privacy/security statement or avoid using the skill. Finally, clarify the metadata inconsistency around config paths with the publisher if you require stronger guarantees.

Getting Started

Got raw footage to work with? Send it over and tell me what you need — I'll take care of the AI clip editing.

Try saying:

• "create a 3-minute raw phone recording into a 1080p MP4"
• "trim the best 30 seconds and add smooth transitions"
• "generating short shareable clips from long recordings for TikTok creators"

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.

Video Clip Maker — Trim and Export Video Clips

Send me your raw footage and describe the result you want. The AI clip editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute raw phone recording, type "trim the best 30 seconds and add smooth transitions", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter source clips under 2 minutes process significantly faster.

Matching Input to Actions

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

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

• X-Skill-Source: video-clip-maker
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

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.

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 → "trim the best 30 seconds and add smooth transitions" → 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 "trim the best 30 seconds and add smooth transitions" — 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 all platforms.