Free Video Ai

Skip the learning curve of professional editing software. Describe what you want — trim silences, add captions, and export as MP4 — and get edited MP4 videos...

Security Scan

The skill's claims line up with its instructions: it uploads user videos to a cloud rendering backend and uses a single service token (NEMO_TOKEN); nothing in the SKILL.md asks for unrelated credentials or system-wide access, but it will send your videos and session tokens to an external service, so treat those as sensitive.

Purpose & Capability

The name/description (AI video editing, trim/captions/export) matches the runtime instructions and API endpoints. Requiring a single service token (NEMO_TOKEN) is expected. Minor metadata inconsistency: the registry summary indicated no required config paths, but the skill frontmatter references ~/.config/nemovideo/ — this is likely benign but worth noting.

Instruction Scope

Instructions remain focused on editing/upload/upload flow and session management with the nemo backend. They include network calls (anonymous token creation, session creation, SSE streaming, upload and render endpoints) and instruct the agent to inspect the install path to set X-Skill-Platform — that implies simple filesystem probing (home path checks). The skill also instructs not to expose tokens/raw API output. There is no instruction to read unrelated user files or to exfiltrate arbitrary system data, but the skill will transmit user-supplied videos and session tokens to the external API (expected for this purpose).

Install Mechanism

Instruction-only skill with no install spec or code files. This is the lowest-risk install model; nothing is written to disk by an installer step according to the manifest.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv). The SKILL.md will generate an anonymous NEMO_TOKEN if none is present by calling the service's anonymous-token endpoint — this is coherent but means the skill can obtain credentials on the fly. The token grants the skill (and backend) the ability to perform uploads and start renders, so it should be treated as sensitive. The frontmatter's reference to ~/.config/nemovideo/ suggests the skill might look for stored configuration there.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request permanent or system-wide privileges, nor does it indicate modifying other skills or system agent settings. Autonomous invocation is allowed (platform default) but not combined with other elevated privileges.

Assessment

This skill appears to do what it says: it uploads your video files to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN (or creates an anonymous one) to run cloud rendering. Before installing or using it: - Treat your videos as being sent to a third-party service — do not upload sensitive or private footage unless you trust the service and its privacy policy. - The NEMO_TOKEN is a credential that allows uploads and rendering; if a token already exists in your environment it will be used, otherwise the skill will fetch an anonymous token. Consider whether you want a token present or to rely on the anonymous flow. - The skill may check your install paths (e.g., ~/.clawhub/, ~/.cursor/) and ~/.config/nemovideo/ to set headers and detect platform; this is minor filesystem probing but worth knowing. - Metadata inconsistency: the registry said no config paths required but the SKILL.md references ~/.config/nemovideo/ — confirm how/where credentials or anonymous tokens will be persisted (if at all). If you are comfortable with videos being processed by mega-api-prod.nemovideo.ai and with the token behavior above, the skill is coherent. If you need guarantees about data retention, encryption, or account binding, ask the publisher for their privacy/security documentation before uploading sensitive content.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim silences, add captions, and export"

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.

Free Video AI — Edit and Export Videos 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 as MP4 — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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 free-video-ai, 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.

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

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.

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)

Tips and Tricks

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

Common Workflows

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