Video Maker Free Easy

Get finished MP4 video ready to post, without touching a single slider. Upload your images or clips (MP4, MOV, JPG, PNG, up to 500MB), say something like "tu...

Security Scan

The skill's declared inputs and runtime instructions match a cloud video-rendering service and are internally consistent aside from a small metadata inconsistency; it does what it says (uploads media and talks to an external API) and doesn't request unrelated secrets or install code on disk.

Purpose & Capability

Name/description (cloud video creation & export) align with required env var (NEMO_TOKEN) and the runtime instructions (upload media, create session, render/export). The token is the expected credential for a third‑party API.

Instruction Scope

Instructions restrict actions to session creation, SSE chat, file upload, state/credits checks and export polling against the nemo API—all consistent with the stated purpose. They do instruct the agent to detect an install path for an attribution header and reference a config path (~/.config/nemovideo/) in the SKILL.md metadata; these file reads are minor but not strictly necessary for core functionality.

Install Mechanism

No install spec and no code files (instruction-only). This is low-risk: nothing is downloaded or written by an installer step.

Credentials

Only one credential is required (NEMO_TOKEN), which is proportionate for a cloud API. The skill documents how to obtain an anonymous token if none is provided. There are no unrelated secrets requested.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request permanent system presence or elevated privileges. Autonomous invocation is allowed by default but is not combined with additional broad access here.

Assessment

This skill uploads whatever media you provide to a third‑party endpoint (mega-api-prod.nemovideo.ai) and uses a service token (NEMO_TOKEN) to act on your behalf. That behavior matches the advertised purpose, but you should: (1) confirm you trust the Nemo service and its privacy/retention policies before uploading private or sensitive files; (2) be aware that an anonymous token issued by the service grants the same upload/render ability for ~7 days (the agent may store it to reuse); (3) note the SKILL.md will try to detect an install path and references ~/.config/nemovideo/ in its metadata — minor filesystem checks may occur to populate an attribution header, though they are not required for core functionality. If any of those are unacceptable, do not install or share sensitive media.

Getting Started

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

Try saying:

• "create my images or clips"
• "export 1080p MP4"
• "turn these photos into a 30-second"

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.

Video Maker Free Easy — Create and Export Videos Fast

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

Say you have five product photos and a logo file and want to turn these photos into a 30-second promo video with music and text — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using 5-10 images keeps the process fast and the output tight.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-maker-free-easy, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these photos into a 30-second promo video with music and text" — 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 all platforms and devices.

Common Workflows

Quick edit: Upload → "turn these photos into a 30-second promo video with music and text" → 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.