Video Trim Hd

Skip the learning curve of professional editing software. Describe what you want — trim the first 30 seconds and cut the last 2 minutes to keep only the high...

Security Scan

The skill's declared purpose (cloud video trimming) matches most of its behavior, but there are inconsistencies around required configuration/credentials and a few runtime file/system checks that warrant caution before installing.

Purpose & Capability

The skill claims to call a NemoVideo cloud API to trim videos and requires a NEMO_TOKEN credential — which is appropriate for a cloud video service. However, the runtime instructions implement an anonymous-token fallback (POST to /api/auth/anonymous-token) so NEMO_TOKEN is not strictly required; the registry metadata declares no config paths while the SKILL.md frontmatter advertises ~/.config/nemovideo/ as a config path. These mismatches are unexplained but could be benign (optional token vs. preferred account token).

Instruction Scope

Instructions are focused on uploading video files, creating sessions, streaming SSE events, and polling render status — all consistent with video trimming. They require access to user video file paths for multipart uploads and describe detecting an install path (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform headers, which implies reading some filesystem locations. This file-system probing is not strictly necessary for functionality and should be disclosed/limited to avoid unexpected reads.

Install Mechanism

No install spec or code files are present; this is an instruction-only skill so nothing is written to disk by an installer. That minimizes install-time risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as primary, which aligns with using a remote service. But SKILL.md will obtain an anonymous token itself if NEMO_TOKEN is missing, so requiring the env var in the registry is inconsistent. No unrelated secrets are requested.

Persistence & Privilege

The skill is not flagged always:true and does not request system-wide changes. Autonomous invocation is allowed (default) but not combined with broad credential or persistence requirements.

What to consider before installing

This skill appears to do what it says (upload your video to a NemoVideo cloud API and return a trimmed file), but note these cautions before installing: - Credential behavior: The registry lists NEMO_TOKEN as required, but the instructions will request an anonymous token from the external API if NEMO_TOKEN is not present. Decide whether you want the skill to obtain short-lived anonymous credentials on your behalf or provide your own NEMO_TOKEN from a trusted account. - File access: The skill will read video files you ask it to upload; it also instructs probing certain paths to set an attribution header (e.g., ~/.clawhub/, ~/.cursor/skills/). Confirm the skill will only read user-specified files and not scan arbitrary directories or sensitive files. - External endpoint: All network activity goes to https://mega-api-prod.nemovideo.ai. Only proceed if you trust that domain/service and its privacy/security practices. Avoid uploading sensitive or private videos unless you have an account and understand retention/processing policies. - Metadata mismatch: The SKILL.md frontmatter and registry metadata disagree about config paths and the necessity of NEMO_TOKEN. Ask the publisher (or request the full, signed skill manifest) to clarify whether NEMO_TOKEN is required, what the ~/.config/nemovideo/ path is used for, and whether the skill logs or transmits extra context. What would increase confidence: an official homepage or publisher reputation, a clear statement that only explicit user-selected files are read and uploaded, and a manifest update that removes contradictory declarations (either require NEMO_TOKEN or document anonymous-token fallback).

Getting Started

Share your video clips and I'll get started on HD 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"

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 Trim HD — Trim and Export HD Videos

This tool takes your video clips and runs HD video trimming through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 10-minute raw recording at 1080p and want to trim the first 30 seconds and cut the last 2 minutes to keep only the highlight — 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 if possible.

Matching Input to Actions

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

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

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.

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.

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

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)

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 first 30 seconds and cut the last 2 minutes to keep only the highlight" → 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 last 2 minutes to keep only the highlight" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

H.264 codec gives the best balance of quality and file size for 1080p output.