Clip Editor Online

Skip the learning curve of professional editing software. Describe what you want — trim the best parts, add transitions, and export as a short clip — and get...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video editing service: it needs a single service token (NEMO_TOKEN), makes expected API calls to a nemo-video backend, and has no install step or unrelated credential requests.

Purpose & Capability

Name/description (cloud clip editing) match the runtime instructions (upload, session creation, SSE chat, render/export). Minor inconsistency: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry summary lists no required config paths; this is a bookkeeping mismatch but consistent with a client that might read its own config directory.

Instruction Scope

Instructions stay within the editing use case: upload media, create/refresh a session token, send SSE edit commands, poll exports. The agent is instructed to upload user files (video/audio/images) and make network calls to mega-api-prod.nemovideo.ai — this is expected for a cloud editor but has privacy implications (user media will be transmitted to that service).

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk by an installer. Low installation risk.

Credentials

Only one credential (NEMO_TOKEN) is required — appropriate for a cloud API. The SKILL.md will also fall back to obtaining an anonymous token via an API call if NEMO_TOKEN is absent. The frontmatter's mention of ~/.config/nemovideo/ is plausible but inconsistent with the registry's 'none' entry for config paths; users should confirm whether the skill will read that local config directory.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. Autonomous invocation is allowed (platform default) but there is no indication it modifies other skills or system-wide settings.

Assessment

This skill appears to do what it says: it uploads media to a nemo-video backend, edits via SSE and returns a download URL. Before installing, consider: 1) Privacy — your video/audio will be uploaded to https://mega-api-prod.nemovideo.ai; verify the service and its privacy terms. 2) Token handling — the skill uses NEMO_TOKEN (or will request an anonymous token on your behalf); ensure the token's scope is limited and you trust the provider. 3) Local config — the SKILL.md references ~/.config/nemovideo/ (the registry metadata omits it); confirm whether the skill will read that path and what it contains. 4) If you need stricter control, do not provide a permanent NEMO_TOKEN; prefer ephemeral/anonymous tokens or review network activity. Overall the skill is coherent, but review the third-party service and privacy before use.

Getting Started

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

Try saying:

• "edit a 2-minute raw video clip from a phone into a 1080p MP4"
• "trim the best parts, add transitions, and export as a short clip"
• "trimming and assembling short clips from raw footage 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.

Clip Editor Online — Edit and Export Video Clips

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

Say you have a 2-minute raw video clip from a phone and want to trim the best parts, add transitions, and export as a short clip — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

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

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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is clip-editor-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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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

Common Workflows

Quick edit: Upload → "trim the best parts, add transitions, and export as a short clip" → 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 parts, add transitions, and export as a short clip" — 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 platforms.