Editor Ab2n

Skip the learning curve of professional editing software. Describe what you want — cut out silences, add background music, and export as MP4 — and get edited...

Security Scan

The skill's instructions and API usage align with a cloud video-editing service, but there are inconsistencies about local config access and privacy implications of uploading video to an external API that you should understand before installing.

Purpose & Capability

The skill's description and runtime instructions consistently target a cloud video-editing backend and legitimately require an API token (NEMO_TOKEN). However, the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch suggests the skill may try to read a local config file (potentially containing credentials) that wasn't declared in the registry.

Instruction Scope

SKILL.md is instruction-only and stays largely within the stated purpose: creating sessions, uploading video files, running edits via SSE, and fetching rendered outputs from mega-api-prod.nemovideo.ai. It explicitly instructs not to expose tokens or raw API outputs. The instructions require uploading user-provided videos to an external cloud service — expected for this functionality but a notable privacy/data-exfiltration surface that the user must accept.

Install Mechanism

There is no install spec and no code files (instruction-only). That minimizes risk from arbitrary code being downloaded or executed on the local machine.

Credentials

The declared primary credential (NEMO_TOKEN) is proportionate for a cloud API. But the SKILL.md frontmatter requests a local config path (~/.config/nemovideo/) which was not listed in the registry metadata — this is disproportionate or at least undeclared access to local files and could expose local credentials or settings. The skill will also upload potentially sensitive video data to an external domain, which is a privacy risk.

Persistence & Privilege

The skill does not request always:true and is user-invocable. It does not declare modifications to other skills or system-wide settings. Session tokens are short-lived (session_id) and the anonymous tokens are described as 7-day ephemeral tokens.

What to consider before installing

This skill appears to be a cloud video editor and needs an API token (NEMO_TOKEN) and will upload any video you provide to mega-api-prod.nemovideo.ai. Before installing/providing credentials: (1) Confirm the service owner and privacy/terms (no homepage is provided here). (2) Prefer using the anonymous token flow rather than supplying a long-lived personal token. (3) Do not upload sensitive or private videos until you verify the backend and storage/retention policy. (4) Ask the maintainer to resolve the inconsistency: SKILL.md frontmatter references ~/.config/nemovideo/ — clarify whether the skill will read that local path and why it wasn't declared in the registry. (5) If you must proceed, test first with non-sensitive sample files and monitor what tokens/headers are being sent.

Getting Started

Send me your raw video footage and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute unedited screen recording into a 1080p MP4"
• "cut out silences, add background music, and export as MP4"
• "editing raw footage into polished videos quickly for content creators"

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.

Editor AB2N — Edit and Export Polished Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute unedited screen recording, ask for cut out silences, add background music, and export as MP4, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing editor ab2n, 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	editor-ab2n
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 "cut out silences, add background music, and export as MP4" — 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 → "cut out silences, add background music, and export as MP4" → Download MP4. Takes 1-2 minutes 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.