Editing Editor Generator

edit raw video footage into edited video files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for auto-editing ra...

Security Scan

The skill is internally consistent with a cloud video-editing service (it uses a single NEMO_TOKEN and remote APIs) but has minor metadata inconsistencies and will transmit uploaded video to a third-party endpoint, so review privacy and token storage before use.

Purpose & Capability

Name/description, declared primary env (NEMO_TOKEN), and the SKILL.md all describe a cloud-based video editing workflow and the listed API endpoints match that purpose. Incoherence: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata noted no required config paths — this mismatch in declared configPaths should be reconciled. Source/homepage are also missing, so origin verification is not possible from provided metadata.

Instruction Scope

Runtime instructions stay within editing/exporting: create or reuse a session, upload video, SSE chat for edits, poll for render, and return download URLs. The skill instructs creating an anonymous token if NEMO_TOKEN is not set and to store session_id for subsequent calls. Minor scope actions: it prescribes detecting the install path to set an attribution header and references a local config dir in frontmatter — both imply reading/writing small local state (session/token) which is plausible but not explicitly specified where/how to persist.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is the lowest-risk model for installation. All runtime behavior is network/API calls.

Credentials

Only one credential is requested (NEMO_TOKEN) which is appropriate for a remote service. The skill also documents an anonymous-token flow (POST to the service to obtain a short-lived token) if NEMO_TOKEN is absent — this is coherent but means the skill will create/hold an access token on your behalf. No unrelated credentials are requested.

Persistence & Privilege

The skill is not marked always:true and does not request elevated or system-wide privileges. It expects to persist a session_id/token for the session lifecycle (normal for this use case). There is no instruction to modify other skills or system-wide settings.

Assessment

This skill appears to be a straightforward cloud-based video editor that will upload your files to mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN (it can automatically request an anonymous token if you don't provide one). Before installing/use: (1) Decide whether you’re comfortable uploading your footage to an external service and review their privacy/terms if available; (2) prefer supplying your own NEMO_TOKEN from a trusted account rather than letting the skill auto-create one if you care about traceability; (3) ask the publisher where session/token data is stored (SKILL.md mentions ~/.config/nemovideo/ in its frontmatter but the registry metadata did not — confirm where persistent data will be written); (4) verify the skill’s origin (homepage/source is missing) if you need an accountable vendor. These are privacy/operational cautions rather than functional red flags; the skill’s requested capabilities are proportionate to its stated purpose.

Getting Started

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

Try saying:

• "edit a 2-minute unedited screen recording into a 1080p MP4"
• "cut the pauses, add transitions, and export a clean final video"
• "auto-editing raw clips into polished videos for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Editing Editor Generator — Edit and Export Polished Videos

Send me your raw video footage 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 unedited screen recording, type "cut the pauses, add transitions, and export a clean final video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing editing editor generator, 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 editing-editor-generator, 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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add transitions, and export a clean final video" — 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 the pauses, add transitions, and export a clean final video" → 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.