Video Editing Ai Auto

Skip the learning curve of professional editing software. Describe what you want — automatically cut dead air, add transitions, and sync to background music...

Security Scan

The skill's instructions mostly match a cloud video-editing integration (it needs an API token and describes upload/render flows), but there are inconsistencies and a few scope/privacy concerns you should review before installing.

Purpose & Capability

The skill name/description align with a cloud video-editing API and the required NEMO_TOKEN credential fits that purpose. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that is not listed in the registry metadata (which said no config paths). That mismatch is unexplained: a pure cloud API integration should not need a local config directory unless it plans to read/write local config files.

Instruction Scope

Instructions are specific about creating anonymous tokens, opening sessions, using SSE, uploading files, polling render status, and returning download URLs — all expected for a remote render service. But the doc also asks to auto-detect an install path to set X-Skill-Platform and references a local config path in frontmatter. Auto-detection would require reading system/install paths; the instructions are vague about how to detect or what files to read. The upload examples use multipart file paths (e.g. -F "files=@/path") which, if followed literally, could cause the agent to read arbitrary local paths instead of only user-provided attachments. These scope items expand the agent's filesystem/network access beyond simple API calls.

Install Mechanism

Instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. This is the lower-risk install model.

Credentials

Only one credential (NEMO_TOKEN) is declared and that aligns with a cloud API. The SKILL.md also documents generating an anonymous token via an API call (100 credits, 7-day expiry) if no token exists; creating such a token is plausible but means the skill may request network calls to mint tokens and (implicitly) store them for the session. The earlier-mentioned config path in frontmatter is not justified by instructions and looks unnecessary for the stated purpose.

Persistence & Privilege

The skill does not set always:true and does not include an install that persists code. It asks to save a session_id returned by the API (expected for session flows) but gives no guidance about secure storage. Autonomous invocation is allowed (platform default) and not combined with an always:true flag or broad unrelated credential access.

What to consider before installing

This skill appears to be a legitimate cloud video-editing integration, but review these before installing: (1) Source and trust — there is no homepage or publisher info; confirm you trust mega-api-prod.nemovideo.ai. (2) Config-path mismatch — the frontmatter references a local config directory (~/.config/nemovideo/) though the registry metadata did not; ask the author why the skill would need to read/write local config. (3) Token handling — the skill will mint an anonymous token if none is provided; ensure you understand where that token will be stored and its permissions/expiry. (4) File access — the upload examples reference local file paths; ensure the agent only uploads files you explicitly attach and does not scan arbitrary filesystem locations. (5) Privacy — uploading video/audio sends content to a third-party service; confirm the privacy/retention policy before sending sensitive footage. If you cannot verify the upstream service or the config-path rationale, treat this skill with caution.

Getting Started

Share your raw video footage and I'll get started on AI auto 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,"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Editing AI Auto — Auto Edit and Export Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI auto editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute unedited phone recording, ask for automatically cut dead air, add transitions, and sync to background music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 2 minutes process significantly faster and yield tighter auto-edits.

Matching Input to Actions

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

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

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

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.

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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

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)

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

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 to background music" — 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.

Common Workflows

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