Clipchamp

Turn a 2-minute screen recording or phone footage into 1080p polished edited videos just by typing what you need. Whether it's editing and exporting videos q...

Security Scan

The skill's requirements and runtime instructions are broadly consistent with a cloud-based AI video-editing client that uses a single service token (NEMO_TOKEN) and uploads user video files to an external API, but there are a few small inconsistencies and privacy/sourcing points you should understand before installing.

Purpose & Capability

The name/description claim cloud-based AI video editing and the SKILL.md only asks for a single service token (NEMO_TOKEN) and details API endpoints for uploading, session creation, and exporting. Requiring NEMO_TOKEN is proportionate to the described remote-rendering capability.

Instruction Scope

The instructions explicitly direct the agent to upload user-provided video files and metadata to https://mega-api-prod.nemovideo.ai and to create/use session tokens. Uploading user files to an external service is expected for this purpose, but it is privacy-sensitive—video and any embedded audio/metadata will be transmitted. The skill also instructs the agent to read or infer install/config paths for attribution headers, which may require examining local paths or config files.

Install Mechanism

Instruction-only skill with no install spec or bundled code, so nothing is written to disk by an installer. This is the lowest-risk install model.

Credentials

Only NEMO_TOKEN is declared as required, which matches the API usage. However the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) even though the registry metadata lists no required config paths — small inconsistency. The anonymous-token flow is provided as a fallback if no token is present, which means the agent will call an auth endpoint to mint a short-lived token if needed.

Persistence & Privilege

always:false and no special system privileges are requested. The skill asks the agent to save session_id/token for the session (normal for a client). It does not request persistent/always-on inclusion or modification of other skills.

Assessment

This skill appears to be a thin client for a cloud video-rendering service and will upload any video files you give it to mega-api-prod.nemovideo.ai for processing. Before installing or using it: 1) Confirm you trust the external domain/owner (source is marked unknown). 2) Don't send sensitive or private footage unless you accept that it will be transmitted and stored/processed by that service. 3) If you don't have a NEMO_TOKEN, the skill will request an anonymous token from the service (creates a short-lived credential); be aware this still transmits a generated client id and may create records on the provider. 4) The SKILL.md suggests reading a local config path and install path to set attribution headers—verify whether your agent implementation will actually read those locations and whether that exposes anything sensitive. 5) If you need higher assurance, ask the skill author for the official source/repository or confirm the domain and ownership before granting token access.

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 editing.

Try saying:

• "edit a 2-minute screen recording or phone footage into a 1080p MP4"
• "trim the clip, add captions, and export for social media"
• "editing and exporting videos quickly for social media or presentations for content creators and marketers"

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.

Clipchamp — Edit and Export Videos Fast

Drop your video clips in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute screen recording or phone footage, ask for trim the clip, add captions, and export for social media, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 5 minutes process and export significantly faster.

Matching Input to Actions

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

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

• X-Skill-Source: clipchamp
• 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.

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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the clip, add captions, and export for social media" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the widest platform compatibility.

Common Workflows

Quick edit: Upload → "trim the clip, add captions, and export for social media" → 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.