Best Video Trimmer

v1.0.0

Get trimmed video clips ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "trim...

0· 35·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for francemichaell-15/best-video-trimmer.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Best Video Trimmer" (francemichaell-15/best-video-trimmer) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/best-video-trimmer
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install best-video-trimmer

ClawHub CLI

Package manager switcher

npx clawhub@latest install best-video-trimmer
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill claims to perform cloud video trimming and its runtime instructions exclusively call a remote rendering API and require a single service token (NEMO_TOKEN). Requiring an API token and uploading videos to the service is coherent with the stated purpose.
Instruction Scope
The SKILL.md explicitly instructs the agent to upload user video files or URLs and to exchange/refresh tokens via the remote endpoints (anonymous-token, session creation, upload, render, etc.). This is expected for a cloud-rendering workflow, but it means user media and metadata will be sent off-host. The doc also describes deriving headers from local install path detection (to set X-Skill-Platform), and saving session_id — these imply accessing local environment/state for attribution and local storage of session data; that behavior is plausible but worth noting.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing is written to disk or downloaded by an install step in the skill bundle itself, which reduces installation risk.
Credentials
Only a single credential (NEMO_TOKEN) is requested, which matches the described cloud API usage. However, the SKILL.md includes metadata that references a config path (~/.config/nemovideo/) not declared in the registry summary — that suggests the skill may read or write a local config directory to store tokens or session info; this is plausible for convenience but is not surfaced in the registry metadata and should be disclosed.
Persistence & Privilege
The skill is not configured as always:true and does not request elevated platform privileges. Autonomous invocation is allowed (the platform default) but there is no evidence this skill requests persistent, system-level presence or modifies other skills' configs.
Assessment
This skill appears to be what it says: a cloud-based video trimming service that uploads your media to nemo-video's API and requires a service token. Before installing or using it: (1) Understand that your videos will be transmitted to https://mega-api-prod.nemovideo.ai — do not upload private/sensitive footage unless you trust that operator. (2) The skill needs a NEMO_TOKEN; use the anonymous-token flow if you prefer temporary tokens rather than providing a long-lived credential. (3) The SKILL.md references storing session info and a local config path (~/.config/nemovideo/); verify where tokens/session IDs are stored and how long they persist on disk. (4) Confirm the privacy/retention policy of the remote service and whether uploaded media or derived assets are retained or used for training. (5) Note a small metadata inconsistency (registry shows no configPaths but the skill's internal metadata lists one) — ask the publisher to clarify what local files are read/written. If you need the skill to never send media off your machine, do not install/use it.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

✂️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk977z40x0esnj08th3pq5v6w4x85nfhc
35downloads
0stars
1versions
Updated 10h ago
v1.0.0
MIT-0

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 first 30 seconds and"

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.

Best Video Trimmer — Trim and Export Clean 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 first 30 seconds and cut the pauses in the middle", 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 points.

Matching Input to Actions

User prompts referencing best video trimmer, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is best-video-trimmer, 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).

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

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

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

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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 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)

Common Workflows

Quick edit: Upload → "trim the first 30 seconds and cut the 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 first 30 seconds and cut the 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 platforms and devices.

Comments

Loading comments...