Free Clip Editor

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

Security Scan

The skill's requests and runtime instructions are consistent with a remote video-editing service: it needs a service token and uploads media to a third‑party API; nothing obvious is requesting unrelated secrets or installing code locally.

Purpose & Capability

Name/description (remote AI video editing) aligns with the required credential (NEMO_TOKEN) and the SKILL.md instructions to call a nemovideo.ai API. Uploading media and requesting renders from a cloud GPU service is coherent with the stated purpose.

Instruction Scope

Instructions are focused on creating a session, uploading videos, running SSE for edits, polling render status, and returning a download URL. They also instruct the agent to detect install path (~/.clawhub, ~/.cursor/skills/) and to read a config path referenced in the SKILL.md metadata (~/.config/nemovideo/) for skill attribution — this implies limited local filesystem probing (presence checks), which is plausible but worth noting. The skill will upload user video files to the external API (expected for this service).

Install Mechanism

Instruction-only skill with no install spec or remote downloads. Nothing is written to disk by an installer; risk from install mechanism is minimal.

Credentials

Only NEMO_TOKEN is declared as required which is appropriate for a hosted service. The SKILL.md also describes obtaining an anonymous token automatically if NEMO_TOKEN is not present, which is a reasonable fallback but means the agent will make network calls to acquire and store/use a token. There is a small inconsistency: registry metadata listed no required config paths, but the SKILL.md frontmatter references ~/.config/nemovideo/ (and instructions read install paths). This discrepancy should be clarified.

Persistence & Privilege

always is false and the skill does not request persistent platform privileges or to modify other skills. Autonomous invocation is permitted by default (platform normal) but is not combined with elevated privileges here.

Assessment

This skill uses a third‑party service (mega-api-prod.nemovideo.ai) to process uploaded video files: your media will be sent to that service and rendered there. Only the NEMO_TOKEN credential is required; if you don’t provide one the skill will request an anonymous starter token from the service. Before installing, verify you trust the nemovideo.ai domain and are comfortable uploading the kinds of media you may provide. Ask the publisher to clarify the config-path requirement (the SKILL.md references ~/.config/nemovideo/ and install-path checks while registry metadata did not), and prefer using an ephemeral/limited token rather than reusing broader credentials. If you need stronger assurance, ask for the service's privacy/terms or prefer an on‑device editor instead.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI clip editing.

Try saying:

• "edit a 90-second raw clip from a phone camera into a 1080p MP4"
• "trim the silent parts, add transitions, and export as a clean short clip"
• "trimming and polishing short video clips for social media for TikTok 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.

Free Clip Editor — Edit and Export Video 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 90-second raw clip from a phone camera, type "trim the silent parts, add transitions, and export as a clean short clip", 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.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: free-clip-editor
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 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 "trim the silent parts, add transitions, and export as a clean 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 all platforms.

Common Workflows

Quick edit: Upload → "trim the silent parts, add transitions, and export as a clean 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.