Editor Online Best

edit raw video clips into polished edited clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for editing videos...

Security Scan

The skill's requests and runtime instructions are largely consistent with an online AI video-editing service, but there are small metadata inconsistencies and privacy considerations you should review before installing.

Purpose & Capability

Name/description (edit video files, cloud rendering, export) align with the runtime instructions: upload endpoints, render/export endpoints, SSE editing flow, and a single service domain (mega-api-prod.nemovideo.ai). The single required credential (NEMO_TOKEN) is appropriate for an API-backed editing service.

Instruction Scope

SKILL.md instructs the agent to upload user video files, create or use a bearer token, manage a session_id, use SSE for interactive edits, poll export status, and synthesize GUI-like responses. These steps are within the editing scope but include: (a) automatic anonymous token acquisition if NEMO_TOKEN isn't present; (b) an instruction to avoid showing raw API responses or token values to the user (this can hide useful debug info); and (c) detection of install path for an attribution header (requires reading the agent's install path). All of these are explainable for the stated purpose but worth noting for privacy and transparency.

Install Mechanism

This is instruction-only with no install spec and no code files — lowest-risk delivery. No downloads, package installs, or archives are performed.

Credentials

Declared primary credential is a single token (NEMO_TOKEN), which fits the service. However, SKILL.md's frontmatter metadata references a config path (~/.config/nemovideo/) that the registry metadata did not list; this mismatch should be clarified. The skill does not request unrelated credentials (e.g., AWS, Git tokens).

Persistence & Privilege

The skill is not always:true and does not request elevated or system-wide privileges. It will store session state and may persist the anonymous token/session_id for the session lifetime, which is reasonable for a web-backed editor.

Assessment

This skill appears to do what it says (remote AI video editing) and only needs one API token, but take these precautions before installing: 1) Confirm the service domain (mega-api-prod.nemovideo.ai) and its privacy/retention policy — uploaded videos will be sent to that backend. 2) Decide whether to set NEMO_TOKEN yourself (so the skill won't auto-create an anonymous token) if you want explicit control. 3) Avoid uploading sensitive or private footage until you verify the provider's terms. 4) Ask the publisher to clarify the metadata mismatch: SKILL.md references ~/.config/nemovideo/ but the registry shows no required config paths. 5) Because SKILL.md says not to show raw API responses/tokens, be aware debugging info may be hidden — if you need transparency during testing, run with a controlled token and test non-sensitive files. 6) If you need higher assurance, request source/homepage or an audited privacy policy from the publisher before use.

Getting Started

Send me your raw video clips 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"
• "trim the pauses, add transitions, and export as a clean MP4"
• "editing videos online without installing software 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.

Editor Online Best — Edit and Export Videos Online

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

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

Matching Input to Actions

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

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

• X-Skill-Source: editor-online-best
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

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 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 "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 for widest compatibility across platforms.

Common Workflows

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