Skill Cutmv Video

cut raw video footage into trimmed edited clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and video editors use it...

Security Scan

The skill's declared purpose (cutting/trimming video via an external NemoVideo API) is plausible and most runtime instructions match that purpose, but there are metadata inconsistencies and a few small scope surprises you should review before installing or using it.

Purpose & Capability

The name/description (video cutting/trimming) align with the runtime instructions (upload, render, export via https://mega-api-prod.nemovideo.ai). Requesting a single service token (NEMO_TOKEN) is appropriate for this purpose. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata provided earlier listed no required config paths — that mismatch is an inconsistency worth clarifying.

Instruction Scope

All instructions are focused on contacting the NemoVideo backend: create session, upload files, SSE messaging, render/poll for output. That matches the stated purpose. Two things to watch: (1) if no NEMO_TOKEN is present the agent will call the anonymous-token endpoint and use that token — the skill will perform network requests and use returned tokens on your behalf; (2) header construction references detecting an install path (e.g., ~/.clawhub/ or ~/.cursor/skills/) to set X-Skill-Platform, which implies the agent may inspect environment/paths to derive headers. There is no instruction that asks for unrelated system files or other credentials.

Install Mechanism

No install spec and no code files — instruction-only skill. This minimizes installation risk because nothing is downloaded or written by an installer.

Credentials

Only one declared credential (NEMO_TOKEN) is required, which is proportional for a cloud-video service. Be aware NEMO_TOKEN likely grants access to render jobs and account credits; the skill also describes generating/using anonymous tokens if no token is present. No other unrelated secrets are requested.

Persistence & Privilege

always is false and the skill does not request permanent platform presence. The skill can be invoked autonomously (default) which is normal — nothing else in the package asks to modify other skills or system-wide configs.

What to consider before installing

This skill appears to genuinely call an external NemoVideo API to process uploads and return rendered videos, but a few things to check before using it: 1) provenance — there's no homepage or source listed; ask the publisher for a homepage, privacy policy, and terms so you know where your uploads go and how long they are retained. 2) credentials — NEMO_TOKEN is the only required secret; treat it like an account credential (it can control renders/credits). Don't paste a real account token unless you trust the service. 3) anonymous tokens — if you don't supply NEMO_TOKEN the skill will request an anonymous token from the external API and use it; this is normal but note tokens may be rate-limited or tied to a client id. 4) uploads — any video you drop will be transmitted to mega-api-prod.nemovideo.ai; avoid uploading sensitive or private footage until you verify data handling. 5) metadata mismatch — SKILL.md references a config path (~/.config/nemovideo/) while registry metadata said none; ask the publisher what, if anything, will be written to your filesystem or configuration directories. If you need higher assurance, request the skill's source or an audited endpoint/owner before installing.

Getting Started

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

Try saying:

• "cut a 3-minute unedited screen recording into a 1080p MP4"
• "cut out the pauses, trim the intro, and export a clean final clip"
• "cutting and trimming raw video footage into clean final clips for content creators and video editors"

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.

Skill Cut MV Video — Cut and Export Edited Videos

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

Here's a typical use: you send a a 3-minute unedited screen recording, ask for cut out the pauses, trim the intro, and export a clean final clip, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter source clips under 2 minutes process significantly faster.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is skill-cutmv-video, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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 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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut out the pauses, trim the intro, and export a clean final 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 platforms and devices.

Common Workflows

Quick edit: Upload → "cut out the pauses, trim the intro, and export a clean final clip" → 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.