Opusclip

convert long-form video into viral short clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it for g...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud-based video clipping service (it needs a NEMO_TOKEN and uploads videos to nemovideo.ai), but there is a minor metadata inconsistency and you should understand that your videos and a generated token will be sent to an external service before installing.

Purpose & Capability

Name/description (video -> short clips) match the required credential (NEMO_TOKEN) and the API endpoints in SKILL.md. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported 'required config paths: none' — this mismatch should be clarified (the skill may read or write a per-user config directory).

Instruction Scope

Runtime instructions stay within the advertised scope: create/refresh an anonymous token if none provided, create a session, upload videos, request renders, poll status, and stream SSE responses. The skill will perform network calls and upload user media to https://mega-api-prod.nemovideo.ai; this is expected for the stated functionality but has privacy implications.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is the lowest-risk install pattern. Any state persistence would come from the agent following the SKILL.md instructions (e.g., storing session_id or token).

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportionate to a cloud API-based video service. Note: the skill’s frontmatter also lists a config path which implies it may read/write ~/.config/nemovideo/ even though registry metadata listed no config paths; that mismatch should be resolved. The skill also instructs generating an anonymous token automatically if NEMO_TOKEN is not present.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It does instruct storing session_id and token for continued use of the backend, but it does not modify other skills or system-wide settings. Autonomous invocation (default) is not itself a concern here.

Assessment

This skill uploads your videos and a generated or provided NEMO_TOKEN to an external API (mega-api-prod.nemovideo.ai). Before installing: 1) Confirm you trust that service and the skill owner (homepage is missing and source is unknown). 2) Decide whether you want to provide your own NEMO_TOKEN (safer) or allow the skill to create an anonymous token (the skill will POST to the vendor to get one). 3) Be aware the skill may read/write a per-user config directory (~/.config/nemovideo/) despite registry metadata not listing it — ask the publisher to clarify. 4) If you have sensitive video content or compliance requirements, do not upload it until you verify vendor policies. If anything about the origin or storage is unclear, request the skill’s source or a trustworthy homepage before proceeding.

Getting Started

Share your long-form video and I'll get started on AI clip extraction. Or just tell me what you're thinking.

Try saying:

• "convert my long-form video"
• "export 1080p MP4"
• "extract the top 5 viral short"

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.

OpusClip — Extract Short Clips from Videos

This tool takes your long-form video and runs AI clip extraction through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 45-minute podcast recording or webinar and want to extract the top 5 viral short clips from this long video — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

Tip: the AI scores each clip by virality potential, so pick clips with higher scores for better engagement.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	opusclip
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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.

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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 → "extract the top 5 viral short clips from this long video" → Download MP4. Takes 1-3 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 "extract the top 5 viral short clips from this long video" — 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 TikTok, Reels, and YouTube Shorts.