Video Editing Ai Automatic

Turn a 3-minute unedited phone recording into 1080p auto-edited videos just by typing what you need. Whether it's automatically cutting and polishing raw foo...

Security Scan

The skill's stated purpose (cloud video auto-editing) matches the network calls and token use, but there are inconsistencies about required credentials and a few scope questions you should understand before installing.

Purpose & Capability

The skill claims to perform cloud-based AI video editing and all runtime instructions call a remote rendering backend (upload, render, export). Requesting a single service token (NEMO_TOKEN) is coherent with that purpose. However, the metadata declares NEMO_TOKEN as a required environment variable while the runtime instructions also describe an anonymous-token fallback path if NEMO_TOKEN is absent — this is an internal inconsistency about whether the env var is mandatory.

Instruction Scope

The SKILL.md gives explicit runtime steps: check NEMO_TOKEN, optionally obtain an anonymous token by POSTing to the provider, create a session, upload video, use SSE or polling to drive edits, and return download URLs. These actions stay within the stated purpose (they upload media and call the editor backend). A mild scope concern: it instructs deriving X-Skill-Platform from the agent's install path (which implies inspecting filesystem locations like ~/.clawhub/ or ~/.cursor/skills/), and it references a config path (~/.config/nemovideo/) in metadata. Those filesystem checks are not necessary to the core editing task and broaden what the agent may read.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be written to disk by an installer. That is the lowest install risk.

Credentials

The skill requests one credential (NEMO_TOKEN), which is proportionate for a cloud service. But the declared 'required env var' vs the documented anonymous-token fallback conflicts: the metadata says NEMO_TOKEN is required, yet the instructions will create an anonymous token if it's missing. Also the skill will upload whatever video files the user provides to a third-party endpoint (mega-api-prod.nemovideo.ai), so granting the skill network access and/or placing NEMO_TOKEN in environment gives it ability to operate on and transmit potentially sensitive media.

Persistence & Privilege

always is false (no forced inclusion) and the skill does not request persistent system privileges or attempt to modify other skills or system configuration. Autonomous invocation is allowed (platform default), which increases operational reach but is not unusual.

What to consider before installing

This skill appears to be a legitimate cloud-based auto-editing integration, but note the following before installing or using it: (1) It will upload any videos you give it to a third-party service at mega-api-prod.nemovideo.ai — don't send sensitive or private footage unless you trust that service. (2) The skill's metadata claims NEMO_TOKEN is required but the instructions will also obtain an anonymous token if none is present; decide whether you want to provide your own token or rely on the anonymous 7‑day token. (3) The skill may inspect install paths or a local config path (~/.config/nemovideo/) to populate headers — consider whether you are comfortable with that filesystem read. (4) There is no published source or homepage; if you need higher assurance, ask the publisher for a code or privacy/security review or prefer a skill with an explicit source and documentation. If you proceed, supply credentials only for services you trust and avoid uploading highly sensitive media.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "automatically cut dead air, add transitions,"

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 Editing AI Automatic — Auto-Edit and Export Polished Videos

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

Say you have a 3-minute unedited phone recording and want to automatically cut dead air, add transitions, and sync music to my footage — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and yield cleaner auto-edits.

Matching Input to Actions

User prompts referencing video editing ai automatic, 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-editing-ai-automatic, 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.

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

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 Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Common Workflows

Quick edit: Upload → "automatically cut dead air, add transitions, and sync music to my footage" → 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 "automatically cut dead air, add transitions, and sync music to my footage" — 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 platform compatibility.