Video Cutter Free

Get trimmed video clips ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "cut...

Security Scan

The skill's requirements and runtime instructions are coherent for a cloud-based video trimming service: it asks for a single service token, uploads user videos to a stated backend, and describes expected API interactions — but there are a few small metadata/instruction mismatches you should be aware of.

Purpose & Capability

The name/description match the actions described (upload video, request cloud render, download result). Requiring a NEMO_TOKEN and calling nemovideo.ai endpoints is consistent. Minor mismatch: the metadata lists a config path (~/.config/nemovideo/) that the SKILL.md does not explicitly read or justify; this could be for cached tokens but is not explained.

Instruction Scope

SKILL.md stays within the service boundary: it instructs uploading media, creating/using a session token, posting chat/edit events (SSE), polling export status, and returning download URLs. It does not instruct reading unrelated system files or other environment variables. It does require sending user video files to an external domain (mega-api-prod.nemovideo.ai), which is expected for a cloud render service but is important for privacy consideration.

Install Mechanism

There is no install spec (instruction-only), so nothing is written to disk or downloaded at install time. This is the lowest-risk install profile.

Credentials

Only one credential is declared (NEMO_TOKEN), which is proportional to a cloud API service. The metadata additionally declares a config path (~/.config/nemovideo/) and asks the agent to auto-detect platform from an install path for an attribution header; these items are not fully justified in the instructions and could require the agent to inspect local paths if implemented — clarify why that access is needed.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide modifications. It can be invoked autonomously (default), which is normal for skills; there is no evidence it would alter other skills or global agent settings.

Assessment

This skill behaves like a normal cloud video editor: it will upload your video files to mega-api-prod.nemovideo.ai and requires a service token (NEMO_TOKEN) or will obtain a short-lived anonymous token for you. Before installing or using it, consider: 1) Do you trust nemovideo.ai with the videos you will upload? Uploaded media may be stored or processed by a third party. 2) Provide a scoped/ephemeral token if possible; NEMO_TOKEN is a bearer credential that grants access to your account/credits. 3) Ask the maintainer why the skill metadata declares ~/.config/nemovideo/ and an install-path platform detection — if the implementation inspects local paths to auto-detect platform it may access more of your environment than the SKILL.md documents. 4) Because the skill performs network I/O and can be invoked autonomously, be cautious about enabling it for highly-sensitive content. If you need higher assurance, request the skill's source or a privacy/data-retention policy from the publisher before use.

Getting Started

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

Try saying:

• "trim my video clips"
• "export 1080p MP4"
• "cut out the first 2 minutes"

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 Cutter Free — Cut and Export Video Clips

This tool takes your video clips and runs AI video trimming 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 cut out the first 2 minutes and trim the ending at 7:30 — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: splitting into shorter segments before uploading speeds up processing.

Matching Input to Actions

User prompts referencing 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-cutter-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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)

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut out the first 2 minutes and trim the ending at 7:30" — 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.

Common Workflows

Quick edit: Upload → "cut out the first 2 minutes and trim the ending at 7:30" → 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.