Trimmer Download

Skip the learning curve of professional editing software. Describe what you want — trim the intro and outro, cut dead air, and export the clean clip — and ge...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud video-trimming tool; it only needs an anonymous session token and performs network calls to the stated API, but there are minor metadata/instruction inconsistencies you should notice before installing.

Purpose & Capability

The skill's name/description (cloud video trimming and download) match the declared primary credential (NEMO_TOKEN) and the API endpoints in SKILL.md. One inconsistency: registry metadata reported no required config paths but the skill's YAML frontmatter lists a configPaths value (~/.config/nemovideo/). This is a minor mismatch in metadata vs. the instruction content.

Instruction Scope

SKILL.md limits actions to obtaining an anonymous token, creating a session, uploading files, polling export jobs, and returning download URLs — all reasonable for a remote render service. It also instructs the agent to infer X-Skill-Platform by checking install paths (e.g., ~/.clawhub/, ~/.cursor/skills/), which requires reading agent runtime paths/filesystem; that check isn't necessary for functionality and expands filesystem access scope slightly but is not obviously malicious.

Install Mechanism

There is no install spec and no code files — this instruction-only skill does not write or execute code on disk, so install risk is low.

Credentials

The skill requests a single credential (NEMO_TOKEN) which is proportionate to communicating with the backend. However, the frontmatter also lists a config path (~/.config/nemovideo/) which suggests the skill may look for local config files; registry metadata elsewhere said no required config paths, so this is an inconsistency to clarify.

Persistence & Privilege

The skill is not always-enabled and uses normal autonomous invocation. It instructs storing a session_id for subsequent API calls (expected behavior) but does not request any elevated platform-wide privileges or modify other skills.

Assessment

This skill appears to do what it says: it contacts nemo video APIs, can create an anonymous token, create sessions, upload video, and poll for exported clips. Before installing, consider: (1) Are you comfortable that your videos are uploaded to https://mega-api-prod.nemovideo.ai? Check the service privacy/retention policy. (2) The skill will auto-create an anonymous NEMO_TOKEN if none is set — that token grants access to the service for 7 days, so verify where the agent stores it (ephemeral memory vs. a file). (3) There's a small metadata inconsistency: the YAML mentions ~/.config/nemovideo/ and also asks the agent to detect its install path — clarify with the author whether the skill will read/write any local config. (4) If you handle sensitive footage, avoid using this skill until you confirm data handling and retention with the service owner. If you want higher assurance, ask the publisher for: (a) confirmation of where tokens/session IDs are persisted, (b) a privacy/retention link for uploaded media, and (c) whether the skill reads any local config files or only uses in-memory state.

Getting Started

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

Try saying:

• "trim a 10-minute raw interview recording into a 1080p MP4"
• "trim the intro and outro, cut dead air, and export the clean clip"
• "cutting and downloading trimmed video clips quickly for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Trimmer Download — Trim and Download Video Clips

Send me your video clips 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 raw interview recording, type "trim the intro and outro, cut dead air, and export the clean clip", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter source clips produce faster exports and smaller download files.

Matching Input to Actions

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

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

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

Common Workflows

Quick edit: Upload → "trim the intro and outro, cut dead air, and export the clean 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.

Tips and Tricks

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