Video Trimmer Download Free

trim 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 and trimming...

Security Scan

This skill is internally consistent with a cloud-based video trimming service: it only needs a NEMO_TOKEN (or will obtain a short-lived anonymous token) and instructs uploading user videos to nemovideo.ai for processing.

Purpose & Capability

The skill's name and description match the runtime instructions: it uploads user video files to a cloud render pipeline, creates sessions, polls for render status, and returns download URLs. Requesting a service token (NEMO_TOKEN) is appropriate for that purpose.

Instruction Scope

Instructions stay within the trimming/export scope (session creation, SSE chat, upload, export/poll). They instruct creating or using a NEMO_TOKEN and uploading files to mega-api-prod.nemovideo.ai. Minor inconsistency: the YAML frontmatter references a config path (~/.config/nemovideo/) even though the registry metadata listed no required config paths; the skill does not otherwise instruct reading arbitrary host files or unrelated credentials.

Install Mechanism

Instruction-only skill with no install spec or code files, so nothing is written to disk or fetched at install time. Low install risk.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportional to a cloud API service. The skill will also obtain a short-lived anonymous token if none is provided. Consider that the token authorizes uploads of user media — supplying a persistent token grants the service ongoing access until revoked.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform-wide privileges or modifications to other skills. It can invoke autonomously (default), which is normal; nothing else in the instructions suggests persistent or cross-skill configuration changes.

Assessment

This skill appears coherent for a cloud video trimming service, but before installing consider: it will upload your video files to https://mega-api-prod.nemovideo.ai — don't send sensitive videos unless you trust that domain and its privacy/retention policies; providing a persistent NEMO_TOKEN gives the service ongoing API access, while the anonymous-token flow issues short-lived credits; verify whether you want that behavior. Note the SKILL.md mentions a local config path (~/.config/nemovideo/) in its metadata even though the registry didn't list config paths—ask the publisher what that is for. If you need stricter control, avoid providing a long-lived token and confirm how uploaded files are stored/retained and who can access download URLs.

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 screen recording into a 1080p MP4"
• "trim the intro and cut out the silent pauses in the middle"
• "cutting and trimming video clips without downloading software 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 Download Free — Trim and Export Video Clips

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 screen recording and want to trim the intro and cut out the silent pauses in the middle — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter source clips process faster — split long videos before uploading.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-trimmer-download-free, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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.

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 intro and cut out the silent pauses in the middle" → 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 intro and cut out the silent pauses in the middle" — 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.