Product Video Cutter Online

Get trimmed product clips ready to post, without touching a single slider. Upload your product video footage (MP4, MOV, AVI, WebM, up to 500MB), say somethin...

Security Scan

The skill's declared purpose (cloud video trimming) matches the API calls it describes and the single required credential (NEMO_TOKEN), but there are small inconsistencies and privacy/telemetry concerns you should understand before installing or uploading sensitive videos.

Purpose & Capability

The name and description (product video cutting) align with the runtime instructions: creating sessions, uploading video files, streaming edits, and requesting renders from https://mega-api-prod.nemovideo.ai. Requesting a single token (NEMO_TOKEN) is proportionate for a hosted service API.

Instruction Scope

Instructions stay within the stated purpose (session creation, upload, SSE, render/polling). However, the SKILL.md instructs generating anonymous tokens and saving them as NEMO_TOKEN, and it describes deriving headers that include an installation path detector (e.g., checking ~/.clawhub/ or ~/.cursor/skills/), which implies the agent may inspect local paths. The SKILL.md does not explicitly instruct reading other system secrets, but the install-path detection and a metadata configPaths entry (~/.config/nemovideo/) could encourage reading local config — ask the author to clarify what local files, if any, the agent will access.

Install Mechanism

No install spec and no code files (instruction-only) — lowest install risk. The skill simply describes remote API usage; nothing is downloaded or written by an installer in the manifest.

Credentials

Only NEMO_TOKEN is required, which is appropriate for a hosted video-processing API. Still, the skill may create and store an anonymous token if none exists. Treat NEMO_TOKEN as a sensitive credential — the skill will use it for all API calls. The metadata references a config path (~/.config/nemovideo/) even though the registry reported no required config paths; this mismatch should be clarified.

Persistence & Privilege

The skill is not set to always:true and does not request system-wide persistence. It does instruct saving a session_id returned by the API (expected for interactive sessions). Autonomous invocation is allowed by default but not combined with other high-risk requests.

What to consider before installing

This skill appears to do what it says (upload your footage to a remote rendering service and return trimmed clips) and only asks for one credential (NEMO_TOKEN). Before installing or using it: - Remember you will be uploading video to an unknown third-party host (mega-api-prod.nemovideo.ai). Do not upload sensitive or confidential footage until you confirm the provider's privacy policy and security practices. - Prefer supplying your own NEMO_TOKEN (if you have one) rather than letting the skill generate an anonymous token, and store that token securely. Treat NEMO_TOKEN as a secret. - Ask the skill author to clarify the metadata inconsistency: SKILL.md includes a configPaths entry (~/.config/nemovideo/) and mentions detecting install paths for headers — confirm whether the agent will read local files or only compute headers from known install locations without reading other config or secrets. - If you are uncomfortable with any local path inspection, do not grant the skill access to your filesystem or run it in an environment with sensitive files. Given the lack of an author homepage or source and the subtle metadata/registry mismatch, exercise caution and seek clarification before uploading real production or private videos.

Getting Started

Send me your product video footage and I'll handle the AI video cutting. Or just describe what you're after.

Try saying:

• "trim a 3-minute product demo recording into a 1080p MP4"
• "cut out the intro and trim the clip to 30 seconds for Instagram"
• "cutting long product videos into short shareable clips for e-commerce marketers"

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.

Product Video Cutter Online — Cut and Export Product Clips

Send me your product video footage and describe the result you want. The AI video cutting runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute product demo recording, type "cut out the intro and trim the clip to 30 seconds for Instagram", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

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

Matching Input to Actions

User prompts referencing product video cutter online, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

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

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)

Common Workflows

Quick edit: Upload → "cut out the intro and trim the clip to 30 seconds for Instagram" → 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 "cut out the intro and trim the clip to 30 seconds for Instagram" — 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 social and e-commerce platforms.