Ai Tools For Video Editing

Turn a 3-minute unedited screen recording into 1080p polished edited clips just by typing what you need. Whether it's automatically editing raw footage into...

Security Scan

The skill's behavior (uploading user video to a nemo cloud backend and using a NEMO_TOKEN) is consistent with its description, but there are metadata inconsistencies and it will send user data to an external service — review before installing or using.

Purpose & Capability

The skill claims to perform cloud-based video editing and the runtime instructions show exactly that (upload, SSE chat, render/export endpoints). Requiring a NEMO_TOKEN is coherent. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not reflected in the registry metadata summary (registry said no config paths) — this mismatch is an incoherence to be clarified.

Instruction Scope

Instructions remain within the video-editing purpose (obtain/validate token, create session, upload video, poll render status). They instruct the agent to read the skill's YAML frontmatter and to detect an install path to populate headers, and to upload raw user video to https://mega-api-prod.nemovideo.ai. This is expected for a cloud editing service, but it does mean user files and generated tokens are sent to an external third party. The skill explicitly instructs not to expose tokens, which is good.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk (nothing is written to disk by an installer).

Credentials

Only one credential is required (NEMO_TOKEN) which fits the stated purpose. The SKILL.md also defines a flow to obtain an anonymous token via the service if none is present, which is plausible. The earlier-mentioned inconsistency between registry metadata (no config paths) and SKILL.md (declares ~/.config/nemovideo/) raises a question about whether the skill expects to read/write local config — that should be clarified before use.

Persistence & Privilege

The skill is not marked always:true. It can be invoked autonomously (default), which combined with the ability to obtain tokens and upload files to an external domain increases the blast radius: an agent could potentially create/use a token and upload data without an explicit user consent step. This is not inherently malicious but is a privacy/systemic risk to be aware of.

What to consider before installing

What to consider before installing or using this skill: - Functionality: This skill will upload your raw videos and editing instructions to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (it can also obtain an anonymous token for you). That is expected for a cloud-based editor — only proceed if you trust that service with your video data. - Metadata mismatch: The SKILL.md frontmatter references a local config path (~/.config/nemovideo/) not listed in the registry metadata. Ask the author which local files/paths the skill will read or write before installing. - Tokens and privacy: The skill uses a bearer token for all requests. Ensure you are comfortable with the token lifecycle (anonymous tokens expire after 7 days per the doc). The skill says not to expose tokens, but confirm whether it persists tokens to disk and where. - Autonomous invocation: Because the agent may call this skill autonomously, check your agent settings and only enable autonomous actions if you want uploads and token creation to possibly occur without a separate explicit approval step. - If you need higher assurance: ask the publisher for a homepage or source repo, verify the nemovideo domain is legitimate, and request explicit statements about what local files/config the skill will access and whether it stores tokens on disk.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "trim the 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.

AI Tools for Video Editing — Edit and Export Polished Videos

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

Here's a typical use: you send a a 3-minute unedited screen recording, ask for trim the dead air, add transitions, and overlay 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 give more precise AI edits.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: ai-tools-for-video-editing
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 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)

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

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.

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 "trim the dead air, add transitions, and overlay 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 for widest compatibility across all platforms and devices.

Common Workflows

Quick edit: Upload → "trim the dead air, add transitions, and overlay 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.