With Ai Free

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

Security Scan

The skill's requests and runtime instructions are consistent with a cloud AI video-editing integration and mostly proportionate, with a small metadata inconsistency to double-check before installing.

Purpose & Capability

Name/description match the runtime instructions: the skill routes uploads and edit requests to nemovideo.ai and requires a NEMO_TOKEN for API calls. One inconsistency: the registry metadata reported 'Required config paths: none' while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). That mismatch should be clarified (does the skill read/write that directory?).

Instruction Scope

SKILL.md gives explicit API endpoints and step-by-step behaviors (session creation, upload, SSE handling, export polling). All instructed actions (POST uploads, poll state, include Authorization header) are within the stated purpose of cloud video editing. It instructs saving a session_id and deriving platform attribution from install paths—saving session IDs is expected but may imply local persistence; the agent is told not to print tokens or raw JSON which is sensible.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. No downloads, packages, or binary installs are requested.

Credentials

The only required credential is NEMO_TOKEN, which is appropriate for an API-backed editing service. The skill also documents how to obtain an anonymous token via the service's auth endpoint. The SKILL.md frontmatter declares a config path (~/.config/nemovideo/); if the skill actually reads/writes that path, that increases its access footprint beyond just the NEMO_TOKEN and should be confirmed. No unrelated secrets are requested.

Persistence & Privilege

Skill is not always-enabled and does not request system-wide privileges. It asks to store a session_id and to detect an install path for header attribution — acceptable for this purpose. Autonomous invocation is allowed by platform default; this is normal and not by itself a red flag.

Assessment

This skill sends your uploaded videos and edit commands to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN (or it will mint a short-lived anonymous token) to authenticate. Before installing: (1) confirm you're comfortable uploading your video content to that external service and review its privacy/terms, (2) prefer using an anonymous token or a revocable limited credential rather than a long-lived secret, (3) ask the author whether the skill will read or write ~/.config/nemovideo/ (the SKILL.md frontmatter lists that path but the registry metadata did not), and (4) remember the agent can invoke skills autonomously by default—only install if you trust the service to handle your media and metadata.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI video editing.

Try saying:

• "edit a 2-minute raw screen recording into a 1080p MP4"
• "trim silences, add captions, and export for free"
• "editing videos with AI tools at no cost for content creators"

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.

With AI Free — Edit Videos Using AI Free

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

Say you have a 2-minute raw screen recording and want to trim silences, add captions, and export for free — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster on the free tier.

Matching Input to Actions

User prompts referencing with ai free, 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 with-ai-free, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim silences, add captions, and export for free" — 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.

Common Workflows

Quick edit: Upload → "trim silences, add captions, and export for free" → 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.