Trimmer Free Online

trim raw video clips into trimmed video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for cutting unwanted...

Security Scan

The skill's requirements and runtime instructions are broadly consistent with a cloud video-trimming service, but there are small metadata inconsistencies and privacy considerations you should review before use.

Purpose & Capability

The skill claims to trim video and all required capabilities (network calls to a trimming backend, a single service token NEMO_TOKEN) match that purpose. Nothing in the SKILL.md asks for unrelated cloud credentials or platform-level privileges. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reports no required config paths.

Instruction Scope

Runtime instructions stay within the trimming workflow: check/use NEMO_TOKEN, obtain an anonymous token if absent, create a session, upload files, stream SSE events, and request exports. The SKILL.md also tells the agent to detect install path (~/.clawhub/, ~/.cursor/skills/) to set attribution headers — reading those paths is not strictly necessary for trimming and is an additional filesystem probe to be aware of. The skill will upload user files to an external API (the expected behavior for a cloud-trimming service).

Install Mechanism

No install spec and no code files — this is instruction-only and does not install third-party binaries or download archives. That minimizes install-time risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as required, which is appropriate for a third-party trimming API. However, SKILL.md indicates it will generate an anonymous token via the service and treat that as NEMO_TOKEN, and the frontmatter lists a config path (~/.config/nemovideo/) not declared elsewhere. The skill also instructs storing session_id for subsequent calls — expected for a session-based API but persistent storage behavior should be confirmed by the platform.

Persistence & Privilege

always:false (normal). The skill asks to keep a session_id and token for requests, which is reasonable for a sessioned API. It does not request modifications to other skills or system-wide settings.

Assessment

This instruction-only skill appears to do what it says: it uploads videos to a cloud backend and returns trimmed exports using a single service token. Before installing, consider: (1) Privacy — your uploaded videos will be sent to https://mega-api-prod.nemovideo.ai; do not upload sensitive or private footage without reviewing the service's privacy/terms. (2) Token behavior — if NEMO_TOKEN is not provided the skill will obtain an anonymous token automatically; decide if you want the skill to generate/store that token for you. (3) Metadata mismatch — the skill's frontmatter mentions a local config path (~/.config/nemovideo/) and asks the agent to probe install paths for attribution; if you prefer zero filesystem probes, ask the maintainer to remove that requirement. (4) Source verification — there is no homepage or source listed; if you need higher assurance, request source code or a reputable homepage from the owner before use. If you accept those trade-offs, the skill's footprint is proportionate to its stated purpose.

Getting Started

Send me your raw video clips and I'll handle the AI video trimming. Or just describe what you're after.

Try saying:

• "trim a 3-minute vlog with long pauses and unwanted sections into a 1080p MP4"
• "trim the intro silence, cut the middle section from 0:45 to 1:20, and remove the last 30 seconds"
• "cutting unwanted segments from videos without downloading software 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 Free Online — Trim and Export Video Clips

This tool takes your raw 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 3-minute vlog with long pauses and unwanted sections and want to trim the intro silence, cut the middle section from 0:45 to 1:20, and remove the last 30 seconds — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster than longer files.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the intro silence, cut the middle section from 0:45 to 1:20, and remove the last 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 all platforms and devices.

Common Workflows

Quick edit: Upload → "trim the intro silence, cut the middle section from 0:45 to 1:20, and remove the last 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.