Editor Online Generator

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 declared purpose (cloud video editing) matches most of its instructions, but there are several inconsistencies and privacy-sensitive behaviors (automatic anonymous token creation, uploads to an external domain, and a metadata/config-path mismatch) that merit caution before installing.

Purpose & Capability

The skill claims to perform cloud video editing and only requires a NEMO_TOKEN — which is appropriate for a hosted editing service. However, the SKILL.md frontmatter advertises a required config path (~/.config/nemovideo/) while the registry metadata listed earlier showed no required config paths; that mismatch is inconsistent and should be clarified. Otherwise, the endpoints and actions described (upload, render, export) align with the stated purpose.

Instruction Scope

The instructions direct the agent to automatically contact an external backend (mega-api-prod.nemovideo.ai), generate an anonymous token if no NEMO_TOKEN is present, create sessions, upload user media, and poll for job status. Automatically obtaining and using an anonymous token and immediately interacting with the remote API (including uploading potentially sensitive video files) can occur without an explicit, separate user consent step in the flow described. The skill also instructs the agent to read metadata from the skill file and to infer platform from install path — this requires local inspection beyond simple in-memory operations. The scope of data sent to the remote service (user videos, metadata, timelines) is significant and not gated by additional prompts in this SKILL.md.

Install Mechanism

This is instruction-only with no install spec or downloaded code, which minimizes disk-write risk. No third-party packages or external installers are pulled by the skill itself.

Credentials

The skill requests a single environment variable (NEMO_TOKEN), which is proportional to a cloud service that requires an auth token. However, the skill will auto-generate and use an anonymous token if NEMO_TOKEN is absent — meaning the agent will initiate outbound auth flows automatically. Also, SKILL.md frontmatter references a config path (~/.config/nemovideo/) not declared elsewhere; this discrepancy should be clarified (reading or writing that path could expose or persist tokens).

Persistence & Privilege

always is false and the skill does not request elevated or persistent platform-wide privileges. It will store a session_id/token for the editing session per its instructions, which is normal for a remote service integration, but the storage location/mechanism is not specified.

What to consider before installing

This skill implements a cloud video editor and will upload your files to https://mega-api-prod.nemovideo.ai and perform server-side processing. Before installing, consider: 1) Privacy: you may be sending raw video (potentially sensitive) to an unfamiliar domain — verify the provider and privacy policy. 2) Automatic connection: if NEMO_TOKEN is missing the skill will automatically generate an anonymous token and call the remote API; decide whether you want that to happen without an explicit confirmation step. 3) Token storage: the skill instructs storing session tokens but doesn't say where; ask where tokens/session IDs are saved and how long they persist. 4) Metadata mismatch: the SKILL.md frontmatter references a config path (~/.config/nemovideo/) that the registry listing did not — ask the publisher to clarify whether the skill will read or write that path. If you proceed, prefer providing your own vetted token (NEMO_TOKEN) instead of allowing anonymous generation, and avoid uploading videos you wouldn't want shared with a third-party service.

Getting Started

Got video clips 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 raw screen recording into a 1080p MP4"
• "trim the pauses, add transitions, and export as a clean MP4"
• "editing and generating polished videos directly in the browser 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 Generator — Edit and Generate Videos Online

Send me your 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 raw screen recording, type "trim the pauses, add transitions, and export as a clean MP4", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

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

Matching Input to Actions

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

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

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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 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

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and export as a clean MP4" → Download MP4. Takes 30-60 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 for widest compatibility across platforms.