Video Maker For Free

Turn five product photos and a logo file into 1080p ready-to-share videos just by typing what you need. Whether it's creating videos from photos or clips wit...

Security Scan

The skill is mostly coherent with a remote video-rendering service but has a few inconsistencies and privacy/storage implications (automatic anonymous token issuance, required env/config entries, and session storage) that you should understand before installing.

Purpose & Capability

The skill's declared purpose (creating videos from uploaded images/clips) matches the API endpoints and actions described in SKILL.md. However the registry metadata states NEMO_TOKEN is a required env var and lists a nemovideo config path, while the runtime instructions explicitly allow generating an anonymous token if none is present — this is inconsistent (it both 'requires' and can auto-obtain a token). The config path requirement (~/.config/nemovideo/) is plausible but not strictly necessary for an instruction-only skill.

Instruction Scope

Runtime instructions stay within the stated purpose: they upload files, create sessions, stream events (SSE), check credits, and start exports. The skill instructs network calls only to the nemovideo API domain; it does not tell the agent to read unrelated system files or credentials. It does instruct detection of install-paths to populate an attribution header (X-Skill-Platform), which requires checking common skill install folders in the user's home directory — a limited filesystem probe but still outside pure video-processing logic.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only. That minimizes risk because nothing is downloaded or written by an installer. All execution is network calls to the external service.

Credentials

Only a single credential (NEMO_TOKEN) is declared, which is appropriate for a cloud video service. But the SKILL.md both requires NEMO_TOKEN (metadata) and describes an anonymous-token flow if it is missing; this overlap is confusing. The metadata also requests a config path (~/.config/nemovideo/) which implies the skill may persist tokens or session state to disk — reasonable for session management but worth verifying. No unrelated credentials are requested.

Persistence & Privilege

The skill instructs the agent to 'store the returned session_id' and obtain/store a token when none is provided. It does not set always:true and does not request elevated system privileges, but it implies local persistence of auth/session state (and the metadata points at a config path). You should confirm where and how tokens/sessions are stored and whether they are retained beyond the expected lifetime.

What to consider before installing

What to consider before installing: - Network & privacy: This skill uploads your media to an external domain (mega-api-prod.nemovideo.ai). If your photos or clips are sensitive, do not use this skill unless you trust that service and its privacy/retention policies. - Token behavior: The skill declares NEMO_TOKEN as required but will also obtain an anonymous token for you if none is set. Decide whether you want to supply your own token (paid account) or allow the skill to generate an anonymous one. If you supply a token, confirm it’s treated securely. - Storage: The instructions say to "store" session_id/token and metadata references ~/.config/nemovideo/. Ask or inspect where the agent stores tokens/sessions and whether they are stored in plaintext or cleared after use. If you prefer no local persistence, avoid installing or disable storage. - Attribution header & path probe: The skill will detect install paths to set an X-Skill-Platform header; this requires checking common skill directories in your home (~/.clawhub, ~/.cursor/skills). That’s a limited filesystem check but not strictly required for video processing — be comfortable with that disclosure before proceeding. - If you’re unsure: request the skill author’s homepage or privacy policy, or prefer only using a version of the skill that clearly documents where credentials and session data are stored. If you do proceed, consider using an ephemeral/throwaway NEMO_TOKEN and avoid uploading sensitive content. Confidence note: medium — the skill is broadly coherent for a cloud video-renderer, but the env/config inconsistencies and implicit persistence behavior merit caution and clarification from the author.

Getting Started

Ready when you are. Drop your images or clips here or describe what you want to make.

Try saying:

• "create five product photos and a logo file into a 1080p MP4"
• "combine these photos into a 30-second video with background music and text overlays"
• "creating videos from photos or clips without paid software for small business owners, students, content 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 Maker for Free — Create and Export Videos Free

Send me your images or clips and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload five product photos and a logo file, type "combine these photos into a 30-second video with background music and text overlays", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using 5-10 images gives the AI enough to work with without slowing down rendering.

Matching Input to Actions

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

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.

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

• X-Skill-Source: video-maker-for-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.

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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

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)

Common Workflows

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