Trimmer Cutter

Turn a 10-minute raw interview recording into 1080p trimmed edited clips just by typing what you need. Whether it's cutting and trimming video clips to remov...

Security Scan

The skill's behavior mostly matches a cloud-based video-trimming service, but there are small metadata inconsistencies and the instructions imply probing local paths (to set an attribution header) and always upload user video to an external API — these mismatches and filesystem probing warrant caution.

Purpose & Capability

The name/description (video trimming/cutting) aligns with the instructions (upload video, create session, SSE editing, export). Requesting a single API token (NEMO_TOKEN) is proportionate for a cloud render service. However, the SKILL.md metadata lists a config path (~/.config/nemovideo/) that is not reflected in the registry metadata — a minor incoherence.

Instruction Scope

Runtime instructions direct uploads of user video files and polling the remote API (expected). They also describe deriving an X-Skill-Platform header from an 'install path' by checking local directories (~/.clawhub/, ~/.cursor/skills/) and reference a local config path in the frontmatter — this implies the agent may check the filesystem to determine headers/platform, which is outside a pure 'upload/edit' scope. The skill will POST user data to https://mega-api-prod.nemovideo.ai; uploading potentially sensitive videos to an external service is normal for this service but is a privacy/security consideration that users should know about.

Install Mechanism

No install spec or code files — instruction-only skill. This is low-risk from an install perspective (nothing is downloaded or written by an installer).

Credentials

Only one credential is required (NEMO_TOKEN), which is consistent with using a third-party API. The SKILL.md also documents obtaining an anonymous token if none is present. The presence of a config path in SKILL.md (~/.config/nemovideo/) that wasn't listed in the registry is an inconsistency worth noting; otherwise, there are no unrelated credentials requested.

Persistence & Privilege

The skill is not declared 'always: true' and uses the platform default allowing autonomous invocation. It does not request persistent system-level privileges or modification of other skills' configs in the documentation.

What to consider before installing

This skill will upload the videos you provide to an external service at mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN (or it will obtain a temporary anonymous token automatically). Before installing/use: (1) Confirm you are comfortable with your video content leaving your device and being processed by that remote service; (2) Prefer to supply your own token only if you trust the service and know what that token grants; (3) Be aware the skill's instructions suggest it may check local directories (e.g., ~/.clawhub/, ~/.cursor/skills/, ~/.config/nemovideo/) to set an attribution header — if you prefer to avoid any filesystem probing, do not grant the skill access or run it in an environment without those paths; (4) Note the SKILL.md frontmatter and the registry metadata disagree about config paths — ask the publisher for clarification if you need stronger assurances about what local data the skill will read. If you handle sensitive or regulated footage, avoid using this skill until you confirm the service's privacy/retention policies.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI trim cutting.

Try saying:

• "edit a 10-minute raw interview recording into a 1080p MP4"
• "trim the silent pauses and cut out the blooper at 3:45"
• "cutting and trimming video clips to remove unwanted sections for content 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.

Trimmer Cutter — Trim and Cut Video Clips

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

Say you have a 10-minute raw interview recording and want to trim the silent pauses and cut out the blooper at 3:45 — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter source clips under 5 minutes process significantly faster.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is trimmer-cutter, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

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.

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)

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

Common Workflows

Quick edit: Upload → "trim the silent pauses and cut out the blooper at 3:45" → 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 silent pauses and cut out the blooper at 3:45" — 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.