Ai Video Maker Free Capcut

Skip the learning curve of professional editing software. Describe what you want — combine my clips into a short video with music and transitions — and get e...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based AI video editing service and request only one service token; nothing strongly contradicts the stated purpose, but the skill will contact a third-party API and may obtain/store tokens automatically so you should review that before use.

Purpose & Capability

Name/description match what the SKILL.md instructs: it uses the nemovideo backend (mega-api-prod.nemovideo.ai) to upload clips, run renders, and return MP4s. Declared primaryEnv (NEMO_TOKEN) and the config path (~/.config/nemovideo/) align with a cloud video service.

Instruction Scope

Instructions stay inside the video-editing workflow (session creation, SSE chat, upload, export). Two notable points: (1) the skill will automatically request an anonymous token if NEMO_TOKEN is not set (POST to /api/auth/anonymous-token), and (2) it explicitly instructs not to display raw API responses or token values to the user. Both can be justified by UX/privacy goals but also reduce visibility into what credentials are created/used.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest-risk install profile because nothing is written to disk by an installer step here (though the skill may instruct the agent to store session data).

Credentials

Only one env var (NEMO_TOKEN) is required, which is appropriate for a third-party API. The skill also documents an automatic anonymous-token creation flow, meaning it can operate without a pre-provided token. The declared config path (~/.config/nemovideo/) suggests the skill may persist session/token metadata there — reasonable for this purpose but worth being aware of.

Persistence & Privilege

always:false and no platform-wide modifications are requested. The skill does not request elevated system privileges or modify other skills' configs in the provided instructions.

Assessment

This skill will upload your media to an external service (mega-api-prod.nemovideo.ai) and needs a NEMO_TOKEN for API calls; if you don't provide one it will generate an anonymous token for you and store session state (likely under ~/.config/nemovideo/). Before installing, consider: 1) Do you trust the remote service with your videos (they will be transmitted off-device)? 2) If you want visibility/control, create and supply your own NEMO_TOKEN rather than letting the skill obtain one anonymously. 3) The SKILL.md instructs the agent not to show raw API responses or token values — this can be normal for UX but reduces transparency; if you need full auditability, avoid using the skill or monitor network activity separately. Finally, there is no install script or packaged code to review (instruction-only), so the runtime behavior depends entirely on the remote API — review the service's privacy/terms before sending sensitive content.

Getting Started

Send me your video clips or images and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "create five short phone clips from a weekend trip into a 1080p MP4"
• "combine my clips into a short video with music and transitions"
• "creating short edited videos from raw clips without manual editing for TikTok and Reels creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

AI Video Maker Free CapCut — Create and Export Edited Videos

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

Say you have five short phone clips from a weekend trip and want to combine my clips into a short video with music and transitions — 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 ai video maker free capcut, 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 ai-video-maker-free-capcut, 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)

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

Common Workflows

Quick edit: Upload → "combine my clips into a short video with music and transitions" → 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 "combine my clips into a short video with music and transitions" — 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 social platforms.