Trimmer Software

Turn a 10-minute raw interview recording into 1080p trimmed video clips just by typing what you need. Whether it's cutting down long recordings into clean sh...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud video-trimming service and request only a service token; there are minor metadata inconsistencies to note but nothing that strongly suggests misdirection.

Purpose & Capability

The skill describes a cloud-based video trimming/export service and explicitly requires a NEMO_TOKEN for API calls to mega-api-prod.nemovideo.ai — this matches the stated purpose. Required binaries are none, and the endpoints and flows described are typical for a cloud render pipeline.

Instruction Scope

SKILL.md instructs the agent to upload user media, create sessions, stream SSE messages, and include attribution headers — all within the trimming/export scope. It also recommends hiding technical details from the user. The frontmatter lists a config path (~/.config/nemovideo/) even though the registry metadata reported no config paths; the instructions themselves do not require reading arbitrary host files, but the presence of that config path in frontmatter is an inconsistency to be aware of.

Install Mechanism

No install spec and no code files — instruction-only. This is low-risk from an installation perspective because nothing is downloaded or written to disk by the skill itself.

Credentials

Only one credential (NEMO_TOKEN) is required and is justified by the need to authenticate to the nemovideo backend. The skill describes a fallback anonymous-token flow if no token is present (POST to the provider's auth endpoint). No unrelated credentials or secret sources are requested.

Persistence & Privilege

always is false and the skill is user-invocable with normal autonomous invocation permitted. The skill does not request to modify other skills or system-wide settings and has no install step that would persist additional privileges.

Assessment

This skill appears to do what it says: it uploads media to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN to run cloud renders. Before installing or enabling: (1) confirm you trust nemovideo.ai (your media will be uploaded to their service); (2) provide only a token scoped for this service (avoid reusing high-privilege or unrelated tokens); (3) note the SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) even though the registry metadata omitted it — ask the publisher whether the skill will read that path; (4) if you prefer not to upload media to that domain, don’t supply a persistent NEMO_TOKEN and instead keep uploads local or use an alternative tool. If you want higher assurance, ask the author for a privacy/processing policy and an explanation of the anonymous-token flow and what data the service retains.

Getting Started

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

Try saying:

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

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 Software — Trim and Export Clean Videos

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

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

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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-software
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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)

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

Common Workflows

Quick edit: Upload → "trim the silent pauses and cut out the first 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.