Trimmer Exe

Skip the learning curve of professional editing software. Describe what you want — trim the silent pauses and cut the intro down to 30 seconds — and get trim...

Security Scan

The skill's instructions, required credential (NEMO_TOKEN), and remote API usage are coherent with a cloud video-trimming service, but there are minor metadata inconsistencies and you should be aware that user videos and tokens are sent to an external service.

Purpose & Capability

Name/description match the runtime instructions: the skill routes uploads and trimming requests to a remote video-processing API and requires an API token (NEMO_TOKEN). Required env var is proportional to the stated purpose.

Instruction Scope

Instructions stay within trimming/export scope (creating sessions, uploading video, reading SSE, polling export). They explicitly instruct generating/using a token and saving session_id. They also require sending user video files to a third-party API (expected), and ask to auto-detect 'install path' for X-Skill-Platform which may require inspecting the runtime/install path.

Install Mechanism

This is instruction-only with no install spec or code files — lowest install risk. No downloads or extracted archives are requested.

Credentials

Only NEMO_TOKEN is required (primary credential), which is appropriate for a remote API. However, the frontmatter also lists a config path (~/.config/nemovideo/) while the registry metadata showed no required config paths — this metadata mismatch is unexplained and could cause the agent to read that directory for tokens or config.

Persistence & Privilege

Skill is not always-enabled and does not request elevated privileges or modification of other skills. It will store session tokens for its own workflow, which is expected for a remote-rendering integration.

Assessment

This skill appears to do what it says: it uploads your videos to a remote GPU-backed trimming service and uses a single API token (NEMO_TOKEN) to authenticate. Before installing: (1) confirm you are comfortable uploading the videos (privacy/retention policies) to https://mega-api-prod.nemovideo.ai, (2) be aware the skill may generate and store an anonymous token as NEMO_TOKEN in the agent environment, (3) note the SKILL.md frontmatter references ~/.config/nemovideo/ even though the registry metadata did not — ask the publisher whether the agent will read that path or any local files, and (4) if you need higher assurance, request the skill's source, an official homepage, or documentation for the nemovideo API and verify the domain and ownership.

Getting Started

Share your raw video footage and I'll get started on AI video trimming. Or just tell me what you're thinking.

Try saying:

• "trim my raw video footage"
• "export 1080p MP4"
• "trim the silent pauses and cut"

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.

Trimmer Exe — Trim and Export Video Clips

Send me your raw video footage and describe the result you want. The AI video trimming runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 10-minute unedited screen recording, type "trim the silent pauses and cut the intro down to 30 seconds", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter source clips process faster and give more precise trim results.

Matching Input to Actions

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

Common Workflows

Quick edit: Upload → "trim the silent pauses and cut the intro down to 30 seconds" → 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 silent pauses and cut the intro down to 30 seconds" — 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.