Ai Online Video Editor

edit raw video footage into edited MP4 videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it for ed...

Security Scan

The skill is internally consistent with an online video-editing service: it requires a single service token and its instructions describe expected API calls to a cloud backend — nothing requested looks disproportionate — but there are a few small metadata inconsistencies and you should expect user videos to be uploaded to the external service.

Purpose & Capability

Name/description match the runtime instructions: the SKILL.md describes uploading video, creating a session, sending edits via SSE, and exporting MP4s from a cloud render API. The only required credential (NEMO_TOKEN) aligns with the described cloud service usage.

Instruction Scope

Instructions stay within the video-editing domain (token check, session creation, upload, SSE, export polling). They instruct network calls to https://mega-api-prod.nemovideo.ai and creation of an anonymous token if NEMO_TOKEN is absent — expected for a cloud service. The skill tells the agent to 'not expose tokens' which is good. It also asks to auto-detect an install path to set an X-Skill-Platform header, which implies reading runtime/install metadata (minor scope expansion but not inappropriate).

Install Mechanism

No install spec and no code files — instruction-only skill — so nothing is downloaded or written to disk by an installer. This is the lowest-risk install posture.

Credentials

Only NEMO_TOKEN is required (declared as primary), which is proportionate. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata presented earlier listed no required config paths — this mismatch should be resolved. Also, if NEMO_TOKEN is not provided the instructions call an auth endpoint to obtain an anonymous token and then use it for uploads; that behavior is expected but means the agent will contact and obtain credentials from the external service at runtime.

Persistence & Privilege

always is false and there is no install-time persistence or modification of other skills. The skill will maintain ephemeral session_id values during a session but does not request elevated system privileges or permanent presence.

Assessment

This skill appears to do what it says: it uploads your videos to a cloud rendering backend (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN to authenticate. Before installing, consider: (1) any video you send will be transmitted to that external service — review its privacy/terms; (2) resolve the metadata mismatch (SKILL.md mentions ~/.config/nemovideo/ but registry metadata did not) — if you expect existing local tokens, confirm whether the agent will read that path; (3) decide whether to provide your own NEMO_TOKEN or let the agent obtain an anonymous token (the skill will call the auth endpoint to get one if missing). If you need stronger assurance, ask the author for the service homepage, privacy policy, and a signed statement of where uploads are stored and how long they’re retained.

Getting Started

Send me your raw video footage and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute screen recording or phone video into a 1080p MP4"
• "trim the silent parts, add transitions, and export a clean final cut"
• "editing raw footage into a finished video without desktop software for content creators and marketers"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

AI Online Video Editor — Edit and Export Videos Online

This tool takes your raw video footage and runs AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute screen recording or phone video and want to trim the silent parts, add transitions, and export a clean final cut — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster.

Matching Input to Actions

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

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-online-video-editor
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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.

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)

Common Workflows

Quick edit: Upload → "trim the silent parts, add transitions, and export a clean final cut" → 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 "trim the silent parts, add transitions, and export a clean final cut" — 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 and devices.