Editor Change

Skip the learning curve of professional editing software. Describe what you want — switch the editing style from jump cuts to smooth transitions with backgro...

Security Scan

The skill's requirements and runtime instructions match its stated purpose (cloud-based AI video re-editing); it only asks for a single service token and describes the upload/render workflow without requesting unrelated credentials or installs.

Purpose & Capability

Name/description (clouded video re-editing) align with requested credential (NEMO_TOKEN) and API endpoints for upload, session, and render. Declared config path (~/.config/nemovideo/) and session/state concepts are relevant to a cloud rendering backend.

Instruction Scope

SKILL.md limits actions to authenticating (use existing NEMO_TOKEN or obtain an anonymous token), creating a session, uploading video files, sending SSE edit commands, and polling for render results. It instructs the agent not to expose raw tokens. One minor scope action: it asks the agent to detect its install path to set X-Skill-Platform and references the skill's YAML frontmatter; that requires reading local context/files but is proportional to adding attribution headers.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is downloaded or written to disk by a provided installer. Low install risk.

Credentials

Only NEMO_TOKEN is required (declared as primary). That single credential directly maps to the described cloud API. The skill documents an anonymous-token fallback flow if no token is present, which is consistent with the service model.

Persistence & Privilege

always:false and no unusual persistence or cross-skill configuration changes. The skill can be invoked by the agent (normal behavior) but does not request permanent system-level privileges.

Assessment

This skill appears coherent: it uploads your video to a NEMO cloud backend for editing and needs a single service token (NEMO_TOKEN). Before installing consider: 1) uploaded videos will leave your machine—don't send sensitive footage unless you trust the service; 2) verify the API domain (mega-api-prod.nemovideo.ai) and the service's privacy/retention policy; 3) the skill can generate an anonymous token that lasts ~7 days (100 free credits) so be aware a temporary token may be created and used; 4) check whether you want the agent to read local install/config paths (used only to set attribution headers). If any of these are unacceptable, do not install or provide a production NEMO token.

Getting Started

Share your existing video file and I'll get started on AI editor replacement. Or just tell me what you're thinking.

Try saying:

• "edit my existing video file"
• "export 1080p MP4"
• "switch the editing style from jump"

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 Change — Switch Editing Style, Export Video

This tool takes your existing video file and runs AI editor replacement through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute interview clip edited in the wrong style and want to switch the editing style from jump cuts to smooth transitions with background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: trimming your clip to the essential scenes before uploading speeds up the re-edit process.

Matching Input to Actions

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

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

• X-Skill-Source: editor-change
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "switch the editing style from jump cuts to smooth transitions with background music" — 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 → "switch the editing style from jump cuts to smooth transitions with background music" → 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.