Video Trimmer In Between

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

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video trimming service (it needs a NEMO_TOKEN and uploads video to a remote API), but the source is unknown and there's a small metadata inconsistency to note.

Purpose & Capability

Name/description (trim and rejoin video) map to the declared need for an API token (NEMO_TOKEN) and remote rendering. The skill's network calls and upload requirements are expected for this task. Note: the frontmatter metadata lists a configPath (~/.config/nemovideo/) while the registry lists no required config paths — minor inconsistency in metadata but not necessarily malicious.

Instruction Scope

SKILL.md instructs the agent to check NEMO_TOKEN, optionally obtain an anonymous token from the remote API, create a session, upload files, use SSE for edits, and poll for exports. All described actions are directly related to remote video editing and do not request unrelated files, credentials, or system state. It does instruct adding skill-specific attribution headers and auto-detecting platform from install path (which may require access to runtime path info).

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is downloaded or written to disk by an installer. This is the lowest-risk install model.

Credentials

Only one required environment variable (NEMO_TOKEN / primary credential) is requested and is appropriate for a hosted API. The SKILL.md also supports obtaining a short-lived anonymous token from the service if no token is present. Users should note that this token authorizes uploads of video content to the remote service.

Persistence & Privilege

The skill does not request persistent or elevated privileges; always:false and no install hooks. It will operate remotely and does not ask to modify other skills or system-wide configs. The only small privacy/behavioral note is that the skill suggests the session token carries render job IDs and jobs may be orphaned if the client disconnects.

Assessment

This skill appears to do what it claims: it uploads your videos to nemovideo.ai and performs cloud-side trimming using a NEMO_TOKEN (or a short-lived anonymous token it can fetch). Before installing/using it, consider: 1) Privacy — your video files are sent to a third-party service; avoid sending sensitive content. 2) Credentials — the token grants the service access to create jobs and access uploads; don’t reuse a high-privilege token you use elsewhere. 3) Billing/credits — the skill mentions credit balances and that exports can fail without required headers, so check whether usage could incur charges. 4) Metadata inconsistency — the frontmatter references a config path (~/.config/nemovideo/) while the registry showed none; confirm whether the skill will read or write local config before trusting it. If you need purely local editing (no cloud upload), do not use this skill.

Getting Started

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

Try saying:

• "edit a 3-minute interview clip with a long pause in the middle into a 1080p MP4"
• "remove the section between 0:45 and 1:20 and join the remaining parts smoothly"
• "cutting out unwanted middle sections from a video and rejoining the remaining parts for 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 In Between — Cut and Rejoin Video Sections

Send me your video clips and describe the result you want. The middle section trimming runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute interview clip with a long pause in the middle, type "remove the section between 0:45 and 1:20 and join the remaining parts smoothly", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: set your in and out points precisely using the timestamp input for cleaner cuts than dragging handles.

Matching Input to Actions

User prompts referencing video trimmer in between, 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-trimmer-in-between
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 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)

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 "remove the section between 0:45 and 1:20 and join the remaining parts smoothly" — 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 → "remove the section between 0:45 and 1:20 and join the remaining parts smoothly" → 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.