Ai Video Editor Creator

Get edited MP4 videos ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something like "...

Security Scan

The skill's runtime instructions mostly match an AI video-editing backend, but there are inconsistencies (metadata vs registry) and unexplained filesystem/config access that warrant caution before installing.

Purpose & Capability

The skill claims to be a cloud-based AI video editor and its instructions (uploading videos, creating sessions, rendering/export endpoints) are consistent with that purpose. Requesting a single service token (NEMO_TOKEN) is proportional. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — that mismatch is unexplained and should be clarified.

Instruction Scope

Instructions direct the agent to contact an external API (mega-api-prod.nemovideo.ai), create anonymous tokens if NEMO_TOKEN is absent, upload files (multipart or by URL), and stream SSE responses. They also require adding attribution headers and 'auto-detecting' an install path to set X-Skill-Platform. The need to inspect an install path or a user config directory implies filesystem access beyond simple network calls; that is scope creep relative to a pure API client and should be justified. The doc instructs not to expose tokens, which is good, but it still expects the agent to manage/retain session tokens.

Install Mechanism

This is an instruction-only skill with no install spec or code files — lowest install risk. Nothing will be written to disk by an installer. The runtime behavior will be network calls to the documented backend.

Credentials

Only NEMO_TOKEN is declared as required, which fits a cloud video service. The instructions additionally describe obtaining an anonymous token automatically if NEMO_TOKEN is not present (reasonable). The SKILL.md frontmatter's configPaths entry (~/.config/nemovideo/) suggests the skill might want to read local configuration or credentials, which is not justified by the description and is inconsistent with the registry metadata — this should be explained before trusting the skill.

Persistence & Privilege

The skill is not always-enabled and does not request automatic elevated persistence. It instructs the agent to keep a session_id for the duration of operations, which is normal for a remote rendering workflow. Autonomous invocation is enabled by default on the platform but is not combined here with additional high privileges.

What to consider before installing

This skill looks like a plausible front-end for a third-party video rendering service, but there are a few things to check before installing: 1) The source and homepage are unknown — ask the publisher for source code, a privacy policy, or a published package so you can verify the backend. 2) Confirm what NEMO_TOKEN represents and whether it grants access to billing/paid credits. Don't reuse sensitive credentials from other services. 3) Clarify why the skill would read ~/.config/nemovideo/ or inspect the agent/install path to set X-Skill-Platform — that implies filesystem access beyond simple API calls. 4) Review network destination (mega-api-prod.nemovideo.ai) and consider running in a sandboxed environment if you proceed. 5) If you need higher assurance, request an implementation (code) or a link to official docs/releases rather than an instruction-only skill from an unknown source.

Getting Started

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

Try saying:

• "create my raw video footage"
• "export 1080p MP4"
• "cut the pauses, add background music,"

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 Video Editor Creator — Edit and Export Finished Videos

Send me your raw video footage and describe the result you want. The AI video editing and creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute unedited screen recording, type "cut the pauses, add background music, and export as a polished video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

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

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

Header	Value
X-Skill-Source	ai-video-editor-creator
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

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.

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)

Common Workflows

Quick edit: Upload → "cut the pauses, add background music, and export as a polished video" → 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 the pauses, add background music, and export as a polished video" — 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.