Video Trimmer Editor

Turn a 10-minute raw screen recording into 1080p trimmed edited clips just by typing what you need. Whether it's cutting unwanted sections from raw video rec...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video trimming/editing service: it only needs a NEMO_TOKEN (it can also obtain an anonymous one), will upload video files to the nemo cloud, and does not require unrelated credentials or installs.

Purpose & Capability

The skill name/description (cloud video trimming/export) aligns with required pieces: a service token (NEMO_TOKEN), endpoints for session/upload/export, and an optional config path for nemo config. There are no unrelated credentials or unexpected binaries requested.

Instruction Scope

Instructions tell the agent to read NEMO_TOKEN from the environment (or obtain an anonymous token via the nemo API), create a session, upload video files (path or URL), and poll for render results. They also instruct detecting installation path (~/.clawhub, ~/.cursor/skills/) and reading the skill's frontmatter to set attribution headers. These filesystem checks are explainable for attribution but do cause the agent to inspect a few user-home paths; the skill does not ask to read arbitrary unrelated files.

Install Mechanism

No install spec or external downloads are included; this is an instruction-only skill (lowest install risk).

Credentials

The only required environment credential is NEMO_TOKEN (declared as primaryEnv). The skill's behavior (Bearer auth to nemo endpoints) justifies this. It will create an anonymous token if none is present, which is consistent with the described flow. No other tokens/keys/passwords are requested.

Persistence & Privilege

The skill is not always-enabled and has no install-time persistence. It does not request elevated system privileges or attempt to modify other skills. Its runtime actions are limited to contacting the nemo backend and accessing video files the user supplies.

Assessment

This skill will upload your video files to a third-party service (mega-api-prod.nemovideo.ai) for trimming and rendering and needs a NEMO_TOKEN (it can request an anonymous token if none exists). Before installing/using: 1) Confirm you trust nemo video's privacy/security policy and are comfortable uploading the content you provide (don’t upload sensitive personal or corporate footage). 2) If you prefer control, set your own NEMO_TOKEN in the environment instead of letting the skill obtain an anonymous token. 3) Be aware the agent will check a few home-directory paths (~/.clawhub, ~/.cursor/skills/, ~/.config/nemovideo/) to populate attribution headers — this is minor but inspect these paths if you want to verify what would be read. 4) Because this is a cloud service, consider using local editing tools if you need to keep data entirely offline.

Getting Started

Share your video clips and I'll get started on AI trim editing. Or just tell me what you're thinking.

Try saying:

• "trim my video clips"
• "export 1080p MP4"
• "trim the silent pauses and cut"

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

This tool takes your video clips and runs AI trim editing 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 silent pauses and cut the last 3 minutes — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: splitting your video into segments before uploading speeds up processing.

Matching Input to Actions

User prompts referencing video trimmer editor, 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-editor
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 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 silent pauses and cut the last 3 minutes" → Download MP4. Takes 30-60 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 silent pauses and cut the last 3 minutes" — 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.