Video Movie Maker Free

create video clips into finished movie files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. casual creators use it for assembling persona...

Security Scan

The skill's declared purpose (cloud video rendering) matches the environment requirements and runtime instructions; it asks for a single service token and describes API calls to a single backend, so its pieces are internally coherent though it will send user video data to an external service.

Purpose & Capability

Name/description, declared env var (NEMO_TOKEN), and config path (~/.config/nemovideo/) line up with a cloud video-rendering backend. No unrelated credentials, binaries, or surprising requirements are requested.

Instruction Scope

SKILL.md instructs the agent to auto-obtain an anonymous token if NEMO_TOKEN is missing, create sessions, upload files, read its own frontmatter for attribution, and detect install path to set X-Skill-Platform. Those actions are within the skill's stated purpose but do involve filesystem checks (install path, its own frontmatter) and automatic network calls that will upload user-provided media to an external API.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing on-disk is installed by the skill itself beyond its described use of a config path for tokens/sessions.

Credentials

Only one environment credential is required (NEMO_TOKEN) and it is plausibly needed for the described backend API. Declared config path explains where session/token data would be stored.

Persistence & Privilege

always:false (no forced presence). The skill can be invoked autonomously by agents (platform default). Combined with the skill's behavior of uploading user files to a remote service, that means an agent could perform network uploads when this skill is triggered — this is expected for a cloud-rendering skill but worth noting from a privacy standpoint.

Assessment

This skill appears internally consistent for cloud video rendering, but it will upload any clips you provide to an external service at mega-api-prod.nemovideo.ai and will create/store a short‑lived anonymous NEMO_TOKEN if you don't supply one. Before installing or using it: (1) avoid uploading sensitive videos unless you trust the service and have reviewed its privacy terms, (2) consider supplying your own NEMO_TOKEN rather than letting the skill auto-generate one if you need auditability, (3) be aware the skill stores session/token data under ~/.config/nemovideo/, and (4) if you need higher assurance, verify the backend domain and operator since SKILL.md and the registry list no homepage or known maintainer.

Getting Started

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

Try saying:

• "create three 30-second phone video clips into a 1080p MP4"
• "combine my clips into one movie with transitions and background music"
• "assembling personal or social media movies from raw clips for casual 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.

Video Movie Maker Free — Create and Export Finished Movies

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

Here's a typical use: you send a three 30-second phone video clips, ask for combine my clips into one movie with transitions and 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 60 seconds each process significantly faster and give cleaner results.

Matching Input to Actions

User prompts referencing video movie maker 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.

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

• X-Skill-Source: video-movie-maker-free
• 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 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 one movie with transitions and 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "combine my clips into one movie with transitions and 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 phones, social platforms, and computers.