Free Video Maker Easy

create video clips or images into finished MP4 videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. casual creators and beginners use it...

Security Scan

The skill's declared purpose (cloud video rendering) mostly matches its runtime instructions, but there are small inconsistencies and some behaviors (automatic token generation, reading local frontmatter/install-path, and an undeclared config path) that you should understand before installing.

Purpose & Capability

Name/description (video creation) aligns with the endpoints and actions in SKILL.md (upload, render, export). Requesting a single service token (NEMO_TOKEN) is proportional to the stated cloud backend. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch is an incoherence to be aware of.

Instruction Scope

Instructions are concrete about API endpoints, SSE, uploading files, and polling export status — all relevant to video rendering. They also instruct the agent to: read the skill's YAML frontmatter at runtime, detect install path to set an attribution header, and (if NEMO_TOKEN is absent) POST to an anonymous-token endpoint and treat the returned token as NEMO_TOKEN. Those require local file/metadata access and network calls; they are plausible for this skill but broaden the agent's runtime actions beyond pure network uploads and downloads.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or extracted by an installer in the manifest.

Credentials

Only one env var is required (NEMO_TOKEN), which fits a cloud API-backed video service. The skill will auto-acquire an anonymous token if none is present (POST to /api/auth/anonymous-token) and treat that as NEMO_TOKEN. This is functional but means the skill will perform credential acquisition and use tokens on your behalf; consider the privacy implications for uploaded media and the token's lifetime.

Persistence & Privilege

always is false and there's no install spec; the skill does not request permanent platform-wide presence or elevated privileges. Autonomous invocation is allowed (default) but is not combined here with other high-risk properties.

What to consider before installing

This skill appears to do what it says (upload media, request renders, return download URLs), but check these things before installing: 1) The SKILL.md mentions a local config path (~/.config/nemovideo/) and reading the skill's frontmatter/install path — confirm you’re comfortable with the agent reading those local paths. 2) If you don't already have NEMO_TOKEN, the skill will automatically obtain an anonymous token from mega-api-prod.nemovideo.ai and use it (token grants service access and has a 7‑day expiry); consider whether you trust that third-party service with your media. 3) There is no install binary, so behavior is driven entirely by these runtime instructions — review the endpoints and domain (nemovideo.ai) and privacy policy of that service if available. If you need higher assurance, ask the skill author for: (a) confirmation about whether and where any files or tokens are stored locally (e.g., ~/.config/nemovideo/), and (b) a privacy/data-retention statement from the backend owner.

Getting Started

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

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "combine my clips into one video"

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 Maker Easy — Create and Export Finished Videos

Drop your video clips or images 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 10-second phone clips and a background music file, ask for combine my clips into one video with transitions and music, and about 30-60 seconds 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 30 seconds process significantly faster.

Matching Input to Actions

User prompts referencing free video maker easy, 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: free-video-maker-easy
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

Common Workflows

Quick edit: Upload → "combine my clips into one video with transitions and music" → Download MP4. Takes 30-60 seconds 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 video with transitions and music" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across social platforms and devices.