Best Clip Editor

edit video clips into edited clip files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for trimming and polishing...

Security Scan

The skill's behavior (uploading your videos to a third‑party API and auto‑creating a bearer token) is coherent with cloud clip editing, but there are metadata/instruction inconsistencies and privacy implications you should understand before installing.

Purpose & Capability

The name/description (cloud-based clip editing) aligns with the runtime instructions (upload, session, render endpoints). However the registry metadata and the SKILL.md disagree: the registry listed no config paths while SKILL.md metadata declares ~/.config/nemovideo/; the registry also lists NEMO_TOKEN as required but the instructions include an anonymous-token fallback. These are inconsistencies (likely sloppy packaging) but not proof of malice.

Instruction Scope

The SKILL.md explicitly instructs the agent to upload user media to external endpoints, create sessions, stream SSE responses, and poll render status — all expected for a cloud editor. It also instructs the agent to auto-create an anonymous NEMO_TOKEN if none exists. No instructions request unrelated system files or unrelated credentials, but the skill will transmit potentially sensitive user video/audio content to an unknown third‑party service.

Install Mechanism

No install spec and no code files (instruction-only). Low installation risk: nothing is downloaded or written by an installer in the package itself.

Credentials

Only one credential (NEMO_TOKEN) is declared, which matches the API usage. But it's odd that NEMO_TOKEN is 'required' while SKILL.md provides an anonymous-token creation flow — a packaging mismatch. The SKILL.md also references a config path (~/.config/nemovideo/) not reflected in the registry metadata.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill does not request permanent agent-wide privileges or modify other skills. No elevated persistence is declared.

What to consider before installing

This skill appears to be a cloud video editor and will upload any media you provide to mega-api-prod.nemovideo.ai and use a bearer token (NEMO_TOKEN) for API calls. Before installing: (1) decide whether you are comfortable uploading your videos to an unfamiliar third‑party service; (2) ask the provider (or documentation) how long uploads are retained, how to delete them, and whether content is used for training; (3) note the packaging inconsistencies (declared NEMO_TOKEN vs. anonymous-token fallback and mismatched config path) — they suggest sloppy packaging, not necessarily malicious behavior; (4) if you have a Nemo account and care about access control, consider providing your own NEMO_TOKEN rather than relying on the anonymous flow; (5) avoid uploading sensitive footage unless you verify the service's privacy/security policies.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim the best moments, add transitions,"

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.

Best Clip Editor — Edit and Export Polished Clips

Send me your video clips and describe the result you want. The AI clip editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute raw footage clip from a phone, type "trim the best moments, add transitions, and sync cuts to the beat", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster and give cleaner AI cut suggestions.

Matching Input to Actions

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

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 best-clip-editor, 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).

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "trim the best moments, add transitions, and sync cuts to the beat" → 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 best moments, add transitions, and sync cuts to the beat" — 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 all platforms and devices.