Video Trimmer High Quality

Turn a 10-minute raw interview recording into 1080p trimmed HD clips just by typing what you need. Whether it's cutting unwanted sections from videos without...

Security Scan

The skill's declared requirements and runtime instructions match a cloud video-trimming service and are mostly coherent, but there are a few minor mismatches you should be aware of before uploading video or providing tokens.

Purpose & Capability

The skill claims to be a cloud-based video trimmer and only requests a single credential (NEMO_TOKEN) and network access to mega-api-prod.nemovideo.ai, which is proportionate. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) in metadata, but the registry metadata you provided lists no required config paths.

Instruction Scope

SKILL.md strictly describes creating a session, uploading video files or URLs, streaming SSE chat responses, polling render status, and returning a download URL. It does not instruct reading arbitrary user files or unrelated environment variables. It does instruct detecting install path and reading the skill's YAML frontmatter for attribution headers (reasonable for telemetry/attribution).

Install Mechanism

No install spec or code files are present; this is instruction-only so nothing is written to disk by the skill itself. No external binary or archive downloads are attempted.

Credentials

Only a single credential (NEMO_TOKEN) is required and used for Bearer authorization to the described API. The instructions also provide a flow to request a short-lived anonymous token if none is present. No unrelated secrets or broad system credentials are requested.

Persistence & Privilege

The skill is not marked always:true and does not request persistent system-wide changes. It does ask the agent to detect install path for a header value and to read its own frontmatter for version attribution, which is limited in scope.

Assessment

This skill appears to do what it claims: it uploads video to a cloud render service (mega-api-prod.nemovideo.ai) and returns a trimmed HD file. Before installing/using it: (1) Confirm you trust the remote service and its privacy policy — your uploaded videos will be sent off-device; (2) Only provide an official NEMO_TOKEN if you trust that API key — otherwise use the anonymous-token path the skill describes; (3) Note the small metadata mismatch (SKILL.md mentions ~/.config/nemovideo/ while registry shows none) and that the skill will check the agent install path for an attribution header — if you’re uncomfortable with that filesystem probe, ask for clarification from the skill author or avoid installing; (4) Prefer contacting a published homepage or known owner for verification, since the skill source is listed as unknown.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the precise video trimming.

Try saying:

• "trim a 10-minute raw interview recording into a 1080p MP4"
• "trim the intro silence and cut the last 3 minutes, keep full quality"
• "cutting unwanted sections from videos without quality loss for YouTubers and 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 High Quality — Trim and Export HD Videos

Drop your video clips in the chat and tell me what you need. I'll handle the precise video trimming on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 10-minute raw interview recording, ask for trim the intro silence and cut the last 3 minutes, keep full quality, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter source clips process faster and preserve bitrate more reliably.

Matching Input to Actions

User prompts referencing video trimmer high quality, 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: video-trimmer-high-quality
• 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 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 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

Common Workflows

Quick edit: Upload → "trim the intro silence and cut the last 3 minutes, keep full quality" → 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 silence and cut the last 3 minutes, keep full quality" — 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.