Product Video Cutter Free

trim product video clips into trimmed product clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. e-commerce sellers and marketers use i...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-cutting service: it only needs a service token, uploads user videos to the stated API, and contains no unrelated credential or install demands — but there are minor metadata inconsistencies and privacy considerations to review before use.

Purpose & Capability

The name/description (product video trimming) aligns with the declared requirement (NEMO_TOKEN) and the SKILL.md API endpoints for uploads, SSE editing, and export. No unrelated cloud providers or credentials are requested.

Instruction Scope

The SKILL.md instructs the agent to check NEMO_TOKEN, obtain an anonymous token from an external endpoint if missing, create a session, upload files, stream SSE, poll job status, and return download URLs — all within the expected scope. Notes: it tells the agent not to display raw API responses or token values (reasonable for UX/privacy but worth auditing), and it uses local install-path detection (~/.clawhub/ or ~/.cursor/skills/) to set an attribution header (this requires reading the agent install path).

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That is the lowest-risk install profile.

Credentials

Only a single environment credential (NEMO_TOKEN) is declared as primary, which is proportionate for a hosted video-processing API. Minor inconsistency: the SKILL.md metadata references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch should be clarified (it could be harmless bookkeeping or indicate other assumptions about local config access).

Persistence & Privilege

The skill is not always-enabled, and autonomous invocation is allowed (the platform default). The skill does not request system-wide configuration changes or additional privileges. It does instruct storing session_id for ongoing requests (normal transient state).

Assessment

This skill appears to be what it claims: a cloud-hosted video trimming workflow that needs a service token and uploads your files to https://mega-api-prod.nemovideo.ai. Before installing, consider: 1) Privacy: videos you upload (product demos may include proprietary or personal info) go to the remote service — review that service's privacy/terms. 2) Token handling: the skill will obtain an anonymous token automatically if you don't provide NEMO_TOKEN; if you prefer control, supply your own token rather than letting the agent request one. 3) Metadata mismatch: SKILL.md mentions a local config path (~/.config/nemovideo/) while registry metadata shows none — ask the publisher to clarify whether the skill will read or write local config files. 4) Network transparency: if you want to verify behavior, monitor outgoing requests to the stated domain and avoid providing other unrelated secrets. If you need higher assurance, request source code or a published homepage for the service before use.

Getting Started

Ready when you are. Drop your product video clips here or describe what you want to make.

Try saying:

• "trim a 3-minute product demo recording into a 1080p MP4"
• "cut out the pauses and trim the intro to 10 seconds"
• "cutting and trimming product videos for listings and ads for e-commerce sellers and marketers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Product Video Cutter Free — Cut and Export Product Videos

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

Say you have a 3-minute product demo recording and want to cut out the pauses and trim the intro to 10 seconds — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process fastest and work best for product ads.

Matching Input to Actions

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

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 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)

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 → "cut out the pauses and trim the intro to 10 seconds" → 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 "cut out the pauses and trim the intro to 10 seconds" — 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 Amazon, Shopify, and social platforms.