Video Trimmer Cutter

Skip the learning curve of professional editing software. Describe what you want — trim the first 30 seconds and cut out the pause at 4:20 — and get trimmed...

Security Scan

The skill's requests and runtime instructions broadly match a cloud video-trimming service; nothing appears intentionally deceptive, but there are a few small inconsistencies and privacy considerations to review before installing.

Purpose & Capability

Name/description align with the actions in SKILL.md (upload video, request cloud render, download result). Requiring a single API token (NEMO_TOKEN) is consistent with a cloud backend integration.

Instruction Scope

Most instructions stay on-task (establish session, upload files, poll render status, download URL). The skill instructs the agent to read this file's YAML frontmatter for attribution (expected) and to detect the agent install path by checking ~/.clawhub/ and ~/.cursor/skills/ to set X-Skill-Platform — this requires inspecting filesystem paths beyond the declared config path and is not strictly necessary for core trimming functionality.

Install Mechanism

Instruction-only skill with no install spec or downloaded code — lowest risk from install mechanics.

Credentials

Only NEMO_TOKEN is required (primary credential) which is proportionate for a third-party cloud API. The skill also supports generating an anonymous token by calling the remote API if no token is present. Metadata lists a config path (~/.config/nemovideo/), but runtime instructions reference other install paths (~/.clawhub/, ~/.cursor/skills/) — a small mismatch in declared vs. accessed paths.

Persistence & Privilege

always:false and normal model invocation. The skill does not request permanent presence or attempt to modify other skills or system-wide settings.

Assessment

This skill looks like a straightforward client for the nemo video-rendering API, but it sends your uploaded video files and (if present) your NEMO_TOKEN to https://mega-api-prod.nemovideo.ai. Before installing, consider: (1) Do you trust that external service to process and store your videos? Avoid uploading sensitive or private footage. (2) The skill can obtain an anonymous token itself if you don't provide one — it will make network calls to mint that token. (3) The runtime asks the agent to inspect some filesystem paths to set an attribution header (it references install directories beyond the declared config path); this is a minor inconsistency but means the skill may check for agent install locations. If any of these are unacceptable, do not install the skill. If you proceed, prefer using a limited/throwaway token and review the third‑party service's privacy/security documentation.

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 and cut.

Try saying:

• "edit a 10-minute raw interview recording into a 1080p MP4"
• "trim the first 30 seconds and cut out the pause at 4:20"
• "removing unwanted sections from raw video recordings 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.

Video Trimmer Cutter — Trim and Cut Videos Fast

This tool takes your video clips and runs AI trim and cut 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 first 30 seconds and cut out the pause at 4:20 — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: splitting into shorter segments before uploading speeds up processing significantly.

Matching Input to Actions

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

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

• X-Skill-Source: video-trimmer-cutter
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

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

Common Workflows

Quick edit: Upload → "trim the first 30 seconds and cut out the pause at 4:20" → Download MP4. Takes 20-40 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 first 30 seconds and cut out the pause at 4:20" — 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.