Video Trimmer Hd

v1.0.0

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

0· 87·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 vcarolxhberger/video-trimmer-hd.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Trimmer Hd" (vcarolxhberger/video-trimmer-hd) from ClawHub.
Skill page: https://clawhub.ai/vcarolxhberger/video-trimmer-hd
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 video-trimmer-hd

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-trimmer-hd
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (HD video trimming) match the runtime instructions: the skill calls a cloud rendering API, uploads video files, creates sessions, polls exports, and requires a NEMO_TOKEN for auth — all coherent with a remote video-trimming service.
Instruction Scope
Instructions are explicit about creating sessions, uploading files, sending SSE messages, polling render jobs, and using the NEMO_TOKEN. This stays within the trimmer's scope, but it will POST user files and metadata to https://mega-api-prod.nemovideo.ai and may generate anonymous tokens automatically if NEMO_TOKEN is absent — users should expect network calls and uploads of their video data.
Install Mechanism
No install spec or code is provided (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install mechanism.
Credentials
Only one credential is requested (NEMO_TOKEN), which is appropriate for the described cloud service. The SKILL.md also describes an anonymous-token flow (POST to the vendor API) to generate NEMO_TOKEN if absent — this is plausible but means the agent will contact an external service to obtain credentials. The SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this metadata mismatch is worth clarifying.
Persistence & Privilege
always:false (no forced global presence). The skill will hold a session_id for job workflow; SKILL.md implies setup on first use but does not explicitly state writing tokens/session data to disk. Confirm whether it will persist tokens or client IDs to ~/.config/nemovideo/ (frontmatter mention) before installing if you want to control local persistence.
Assessment
This skill is coherent for cloud-based video trimming: it requires a NEMO_TOKEN and will upload your videos to https://mega-api-prod.nemovideo.ai, create sessions, and poll render jobs. Before installing, confirm (1) you trust the domain and service to handle your video content and privacy, (2) whether the agent will store the anonymously-obtained token or session data locally (frontmatter references ~/.config/nemovideo/ but registry metadata omitted config paths), and (3) you’re comfortable with the skill automatically calling the vendor’s anonymous-token endpoint if NEMO_TOKEN is not provided. If any of those are unacceptable, ask the skill author to clarify token storage and provide an explicit privacy/storage policy or to make token persistence optional.

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

Runtime requirements

✂️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97chzvbf4rx4hq12wfwm7edwh84p9gj
87downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "trim a 10-minute raw interview recording into a 1080p MP4"
  • "trim the first 30 seconds and cut the dead air at the end"
  • "cutting unwanted sections from HD video recordings for content creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

  • Generate a UUID as client identifier
  • POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
  • Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Trimmer HD — Trim and Export HD Videos

Send me your video clips and describe the result you want. The AI precision 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 dead air at the end", 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 preserve the most quality.

Matching Input to Actions

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-trimmer-hd, 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 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 first 30 seconds and cut the dead air at the end" → 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 dead air at the end" — 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...