Editor De Video Online

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

Security Scan

The skill's declared purpose (cloud video editing) matches what its instructions require (a NEMO_TOKEN and calls to nemovideo.ai endpoints); the main risks are privacy (uploading video to an external service) and a small metadata inconsistency about a config path.

Purpose & Capability

The skill is an instruction-only video-editing integration that requires a backend token (NEMO_TOKEN) and makes API calls to a remote video-rendering service. Requesting a service token and POST/upload endpoints is proportional to the stated purpose. One minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) but the registry metadata claimed no required config paths.

Instruction Scope

The SKILL.md clearly instructs the agent to create sessions, stream SSE chat, upload user video files, poll job status, and re-acquire an anonymous token if no NEMO_TOKEN is present. Those actions are within the scope of a cloud editor, but they involve uploading potentially large and sensitive user files and generating anonymous tokens via an external API. The instructions do not ask the agent to read unrelated system files or unrelated environment variables, but the header auto-detection guidance (X-Skill-Platform from install path) could require agent-side path awareness.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That minimizes filesystem risk (nothing is downloaded or extracted).

Credentials

Only one credential is required: NEMO_TOKEN (declared as primaryEnv). That is reasonable for a service that performs authenticated uploads/renders. The skill will also attempt to obtain an anonymous token from the external API if NEMO_TOKEN is not provided — expected behavior but worth noting. No unrelated credentials or secrets are requested.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges or modification of other skills. It does ask for an optional config path (in SKILL.md metadata) that might be used to store tokens, but it does not request system-wide permissions or persistent always-on presence.

Assessment

What to consider before installing: - This skill uploads your video files and metadata to https://mega-api-prod.nemovideo.ai and will use whatever NEMO_TOKEN you provide (or obtain a temporary anonymous token). Treat NEMO_TOKEN like a password — don't supply a sensitive, broadly-scoped credential unless you trust the service. - The skill is instruction-only (no shipped binaries), so there is no hidden code on disk, but network activity will send your media off-platform. If your videos contain sensitive data, do not upload them. - There is a small metadata mismatch: the SKILL.md references storing data under ~/.config/nemovideo/ while the registry listing showed no required config paths; ask the publisher how tokens/cache are stored if you care about local persistence. - If unsure: create and use a throwaway/test NEMO_TOKEN or use anonymous mode with non-sensitive clips, verify the service's privacy/terms, and confirm the domain and owner identity before sending private content.

Getting Started

Share your video clips and I'll get started on AI video editing. Or just tell me what you're thinking.

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "cut the silent parts, add transitions"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Editor de Video Online — Edit and Export 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 "cut the silent parts, add transitions and background music", 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 de video online, 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-de-video-online
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 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)

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

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 silent parts, add transitions and 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 across platforms.

Common Workflows

Quick edit: Upload → "cut the silent parts, add transitions and 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.