Video Extractor

Get extracted video clips ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, MKV, up to 500MB), say something like "ext...

Security Scan

The skill's declared behavior (cloud-based AI clip extraction) matches most of its instructions, but there are small inconsistencies and privacy risks (uploading your videos and use of an external token on an unverified endpoint) that merit caution before installing.

Purpose & Capability

The skill claims to extract video clips and the SKILL.md contains exact API endpoints, upload/export flows, and token usage consistent with that purpose. However, registry metadata shown earlier lists no required config paths while the skill frontmatter requests ~/.config/nemovideo/ — a mismatch. Also there is no homepage/source repo to verify the service operator.

Instruction Scope

Runtime instructions direct the agent to: generate anonymous tokens, POST uploaded videos and metadata to https://mega-api-prod.nemovideo.ai, maintain session IDs, stream SSE and poll export status. These are expected for a cloud render service, but they explicitly send user files (potentially large and sensitive) to a third-party API and require setting/supplying a bearer token. The skill does not instruct reading any unrelated local files, but the frontmatter mentions a config path that is not referenced in the runtime steps.

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 install risk.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required, which is proportionate for an API-backed video service. Still, providing NEMO_TOKEN grants the skill bearer access to the remote account/service, and the skill also supports generating an anonymous token (via POST) if none is present — meaning the agent may either use your token or create one. The frontmatter's configPaths entry is declared but not used by the instructions, which is an inconsistency to verify.

Persistence & Privilege

always is false and model invocation is allowed (the platform default). The skill does not request permanent agent presence or system-level modifications in its instructions.

What to consider before installing

This skill appears to do what it says (cloud-based video clipping), but you should be cautious because it uploads your video files to a third-party domain (mega-api-prod.nemovideo.ai) and uses a bearer token (NEMO_TOKEN). Before installing: 1) Verify the service/operator (homepage, source, privacy policy) — none is provided here. 2) Prefer using an anonymous/ephemeral token or test with non-sensitive sample videos first. 3) Note the frontmatter mentions a config path (~/.config/nemovideo/) even though the registry entry did not—ask the author why and whether the skill will read local config files. 4) If you must provide an account token, ensure it has minimal permissions and can be revoked. 5) If you need stronger assurance, request the skill's source or an audited integration to confirm no unexpected data exfiltration.

Getting Started

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

Try saying:

• "extract my video files"
• "export 1080p MP4"
• "extract the key highlights and save"

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.

Video Extractor — Extract and Save Video Clips

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

Say you have a 30-minute recorded webinar and want to extract the key highlights and save them as separate clips — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: trimming to the exact timestamp before uploading speeds up extraction significantly.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	video-extractor
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.

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)

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

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 "extract the key highlights and save them as separate clips" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "extract the key highlights and save them as separate clips" → Download MP4. Takes 30-90 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.