Video Creator Free

Turn five product photos and a logo file into 1080p finished MP4 videos just by typing what you need. Whether it's creating short videos from photos or clips...

Security Scan

The skill's instructions largely match a remote video-rendering service, but there are small inconsistencies (declared config path present in the SKILL.md but not in registry metadata) and it will upload your files and auto-create tokens on an external domain — review before use.

Purpose & Capability

The skill's name/description describe remote video creation and the runtime instructions call a remote video-render backend (upload endpoints, render/start/export APIs) — this is coherent. Minor incoherence: the registry metadata lists no required config paths, but the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/). That mismatch should be clarified (is the skill going to read or write that path?).

Instruction Scope

SKILL.md instructs only remote API calls (auth, session creation, file upload, SSE streaming, render polling) and handling their responses. Those actions are within the stated purpose. It does automatically acquire an anonymous token if NEMO_TOKEN is not present and directs the agent to store session_id for future requests; these are expected for a remote service but users should be aware files and metadata will be transmitted off-device.

Install Mechanism

No install spec and no code files (instruction-only). This is low-risk from an installation perspective — nothing is written to disk by an installer here (though the runtime may upload files and persist session ids).

Credentials

Only one credential is required (NEMO_TOKEN) which matches the service's Authorization header usage. Proportional overall. Note: SKILL.md also lists a config path in its frontmatter; the registry listing omitted this. Confirm whether the skill will read/write ~/.config/nemovideo/ and whether tokens or session ids are persisted there.

Persistence & Privilege

always is false and the skill is normal user-invocable/autonomous. The skill instructs storing session_id for requests, which is normal. There is no instruction to modify other skills or global agent configuration.

What to consider before installing

This skill appears to really call an external video-rendering backend and will upload whatever images/clips you give it. Before installing or using it: (1) Confirm the service domain (mega-api-prod.nemovideo.ai) is trustworthy and read its privacy policy — sensitive images will leave your device. (2) Decide whether to provide your own NEMO_TOKEN rather than allowing the skill to auto-request an anonymous token. (3) Ask the author to clarify the config-path discrepancy: SKILL.md frontmatter lists ~/.config/nemovideo/ but the registry metadata did not — find out whether tokens or session IDs will be persisted to disk and where. (4) If you need stricter privacy, avoid uploading private media to this service. If you want me to, I can extract the exact API calls and headers the skill will use so you can review them or run them manually.

Getting Started

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

Try saying:

• "create five product photos and a logo file into a 1080p MP4"
• "combine these images into a 30-second video with background music and text overlays"
• "creating short videos from photos or clips without editing software for 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 Creator 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 images 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 fewer than ten images keeps render time under a minute.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-creator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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 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

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.

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 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)

Common Workflows

Quick edit: Upload → "combine these images 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 images 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.