Video Editor Ai Maker

Turn a 2-minute unedited phone recording into 1080p polished edited clips just by typing what you need. Whether it's turning raw footage into finished videos...

Security Scan

The skill's declared purpose (cloud video editing) roughly matches its runtime instructions, but there are inconsistencies and some behaviors that warrant caution before installing or trusting it with sensitive footage.

Purpose & Capability

The name/description match the instructions (cloud rendering, uploads, exports). The skill requires a NEMO_TOKEN which is consistent with a cloud API. However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and other metadata not reflected in the registry summary (registry reported no required config paths). The skill has no homepage or known source, which makes verification harder.

Instruction Scope

The SKILL.md explicitly instructs the agent to read NEMO_TOKEN and, if absent, obtain an anonymous token by POSTing to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token and to perform many network operations (session creation, uploads, SSE streaming, polling). Those network calls are coherent with a cloud video editor. The instructions also derive headers from local install paths and the skill file frontmatter, which requires the agent to inspect file paths and the skill file — this is reasonable but worth noting. No unrelated system files or unrelated credentials are requested.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. All runtime actions are HTTP API calls; nothing will be downloaded or executed locally by the skill itself.

Credentials

The only declared credential is NEMO_TOKEN which is appropriate for a hosted video service. But the SKILL.md instructs the agent to generate and use an anonymous token automatically if NEMO_TOKEN is missing (POST to the external API), and the frontmatter mentions a config path where credentials or state might be stored. The mismatch between registry metadata (no config paths) and SKILL.md (has configPaths) is unexplained. Automatic token creation and unspecified local persistence increase the risk of unexpected external calls or local token storage.

Persistence & Privilege

The skill is not always-enabled and uses normal autonomous invocation defaults. It does not request system-wide privileges or claim to modify other skills. The main persistence risk is session tokens and render jobs kept on the service side; the skill mentions orphaned jobs if a user closes a tab.

What to consider before installing

This skill appears to do what it says (cloud video editing) and only asks for one token (NEMO_TOKEN), but exercise caution before installing or using it on sensitive footage. Things to consider: 1) The skill will call an external domain (mega-api-prod.nemovideo.ai) and will request or auto-create an anonymous token if NEMO_TOKEN is not present — so invoking it will contact that service even without you providing credentials. 2) There is an inconsistency: the SKILL.md mentions a config path (~/.config/nemovideo/) that could imply local persistence of tokens, but the registry metadata showed no required config paths — ask the publisher where (and whether) tokens or files are stored. 3) No homepage or source repo is provided; prefer vendors with a published privacy policy and terms before sending sensitive videos. 4) If you choose to try it, consider creating/using a scoped or limited token (not long-lived credentials), avoid uploading sensitive content until you verify the service, and request documentation from the publisher explaining token issuance, storage, and data retention. If you need higher assurance, ask the publisher for a source repository or a published privacy/security statement before enabling the skill.

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

• "edit a 2-minute unedited phone recording into a 1080p MP4"
• "trim the pauses, add background music, and export as a short reel"
• "turning raw footage into finished videos with AI-assisted cuts and effects for content creators and social media 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.

Video Editor AI Maker — Edit and Export AI Videos

Send me your raw video footage 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 unedited phone recording, type "trim the pauses, add background music, and export as a short reel", 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 and give the AI more precise results.

Matching Input to Actions

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

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

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.

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.

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.

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

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)

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 → "trim the pauses, add background music, and export as a short reel" → 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 pauses, add background music, and export as a short reel" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 with H.264 codec for the widest compatibility across platforms.