Video Editor With Ai Online

Turn a 2-minute unedited screen recording into 1080p edited video clips just by typing what you need. Whether it's editing raw footage into polished videos w...

Security Scan

The skill's requests and runtime instructions largely match a cloud video-editing integration and don't ask for unrelated credentials or installs, though there are small metadata inconsistencies you should be aware of before installing.

Purpose & Capability

The skill's name and description align with the required environment variable (NEMO_TOKEN) and the documented API endpoints on mega-api-prod.nemovideo.ai. It does not request unrelated cloud credentials or binaries. One inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch should be clarified.

Instruction Scope

Runtime instructions are limited to establishing a session, uploading videos, polling render status, and handling SSE — all expected for a remote editor. The instructions do require network calls to the nemo API and to upload user video files (expected). The only notable scope creep is a guidance to detect an install path to set X-Skill-Platform (e.g., ~/.clawhub/, ~/.cursor/skills/) which implies reading the agent's install path or filesystem to populate a header; this is minor but worth noting.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only which minimizes installation risk and disk writes.

Credentials

The skill only requires a single credential (NEMO_TOKEN) which is appropriate for a hosted service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that was not reflected in the registry metadata; if the skill will read that path, confirm why and what it contains. No other secrets or unrelated env vars are requested.

Persistence & Privilege

The skill does not declare always:true, does not install persistent components, and does not request system-wide changes. It uses normal session tokens for server-side jobs. Autonomous invocation is allowed by default (disable-model-invocation is false) — this is platform default and not by itself a concern.

Assessment

This skill appears to do what it says (remote AI video editing) and only asks for a single service token. Before installing, verify that you trust the domain mega-api-prod.nemovideo.ai and are comfortable uploading your videos to that service. Ask the publisher to clarify the metadata mismatch about ~/.config/nemovideo/ (will the skill read that path?), and whether the skill reads the agent install path to set X-Skill-Platform headers. If you don't want the skill to run autonomously, consider disabling model invocation or only enabling the skill when needed. Finally, keep your NEMO_TOKEN separate from other credentials and rotate it if you suspect misuse.

Getting Started

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

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "cut out the pauses, 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.

Video Editor with AI Online — Edit and Export AI Videos

Send me your raw video clips and describe the result you want. The AI-powered 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 out the pauses, add transitions, and put captions on every scene", 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 video editor with ai 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editor-with-ai-online, 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).

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

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)

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

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

Common Workflows

Quick edit: Upload → "cut out the pauses, add transitions, and put captions on every scene" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut out the pauses, add transitions, and put captions on every scene" — 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.