Video Editor Extension

Skip the learning curve of professional editing software. Describe what you want — trim the pauses, add transitions, and export as a clean MP4 — and get edit...

Security Scan

The skill's requirements and runtime instructions match its stated purpose (cloud video editing); it is instruction-only and asks for a single service token, but it will upload user video files to an external API — review privacy before use.

Purpose & Capability

Name/description describe cloud video editing and the skill only requests a single API credential (NEMO_TOKEN) and a config path for nemovideo — these are coherent with a remote-rendering video editor.

Instruction Scope

Runtime instructions direct the agent to upload user video files and poll/render via https://mega-api-prod.nemovideo.ai, including SSE handling and export polling. This is expected for a cloud editor, but it means user media will be transmitted to a third-party service and an anonymous token may be requested automatically if NEMO_TOKEN is not present. The skill explicitly instructs not to expose tokens/raw API output.

Install Mechanism

No install spec or code files — instruction-only skill. This limits local persistence and reduces local-supply-chain risk.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportional. Metadata lists a config path (~/.config/nemovideo/) that could be used to store tokens/session state; SKILL.md also instructs the agent to obtain an anonymous NEMO_TOKEN if none exists. Be aware tokens may be persisted in that config path.

Persistence & Privilege

Skill is not always:true, does not request to modify other skills or system-wide settings, and is user-invocable. It relies on server-side sessions but does not demand elevated local privileges.

Assessment

This skill appears to do what it says: it uploads user videos and controls a cloud render service using a single API token (NEMO_TOKEN). Before installing/using it, consider: 1) Privacy: your raw video files will be sent to https://mega-api-prod.nemovideo.ai — do not upload sensitive footage unless you trust that service and its privacy policy. 2) Token handling: if you don't provide NEMO_TOKEN, the skill will request an anonymous token (100 free credits, 7-day expiry) from the service and may persist session/token info (metadata references ~/.config/nemovideo/). If you prefer control, supply your own NEMO_TOKEN and monitor where it is stored. 3) Attribution headers: the skill requires sending X-Skill-Source/Version/Platform headers on each request (normal for a plugin). 4) No local binaries are installed and no unrelated credentials are requested. If you need higher assurance, audit network calls to the listed domain and review the service's terms/privacy before uploading private content.

Getting Started

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

Try saying:

• "edit a 2-minute screen recording or phone footage into a 1080p MP4"
• "trim the pauses, add transitions, and export as a clean MP4"
• "extending and refining existing video clips with AI-assisted edits for content creators and marketers"

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.

Video Editor Extension — Edit and Export Video Clips

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

A quick example: upload a 2-minute screen recording or phone footage, type "trim the pauses, add transitions, and export as a clean MP4", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: shorter source clips under 3 minutes process significantly faster.

Matching Input to Actions

User prompts referencing video editor extension, 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-editor-extension
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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)

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

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.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and export as a clean MP4" → Download MP4. Takes 30-90 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 pauses, add transitions, and export as a clean MP4" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 with H.264 codec for the widest platform compatibility.