Free Video Maker From Photo

Skip the learning curve of professional editing software. Describe what you want — turn my photos into a slideshow video with music and transitions — and get...

Security Scan

The skill's requests and runtime instructions align with its stated purpose (cloud-based photo→video rendering) but lacks public source/homepage and includes minor metadata that could leak local config info — review before uploading sensitive images or using a long-lived token.

Purpose & Capability

The skill is a cloud video-renderer and only requests a single service credential (NEMO_TOKEN) and references a nemovideo config path; these items match the described API interactions and upload workflow.

Instruction Scope

SKILL.md precisely instructs the agent to create sessions, upload user images, open SSE streams, poll render status, and return download URLs to a single remote host (mega-api-prod.nemovideo.ai). That behavior is expected for a cloud rendering service but does mean user files are uploaded to an external service. The skill also auto-acquires an anonymous token if NEMO_TOKEN is absent.

Install Mechanism

No install spec or code is present (instruction-only), so no binaries or archives will be written to disk during installation.

Credentials

Only NEMO_TOKEN is required (declared as primary). The metadata also lists a config path (~/.config/nemovideo/) and asks to auto-detect an install path for X-Skill-Platform — this is plausible for locating an existing token or platform info but is not strictly necessary for core functionality and could expose local path/config presence.

Persistence & Privilege

The skill is not force-enabled (always:false) and does not request system-wide changes. It can be invoked autonomously by the agent (default), which is normal; nothing in the manifest asks to modify other skills or global settings.

Assessment

This skill appears coherent for turning photos into cloud-rendered videos, but before installing consider: (1) All user images will be uploaded to mega-api-prod.nemovideo.ai — do not send private or sensitive images unless you trust that service and its privacy policy. (2) The skill will use NEMO_TOKEN if present; only supply a token you control and trust. If you don’t want to provide a token, the agent will request an anonymous 7‑day token automatically — that is ephemeral but still sends data to the remote service. (3) Metadata references a local config path and auto-detection of install path; this could reveal whether local config exists or expose a local path string. (4) The skill has no public source or homepage — request the vendor/service URL, privacy policy, or source code before wide use. If you need higher assurance, ask for: the service's official domain verification, a privacy/retention policy, where tokens are stored (if at all), and sample API responses. Revoke any token you supply if you stop using the skill.

Getting Started

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

Try saying:

• "turn my images"
• "export 1080p MP4"
• "turn my photos into a slideshow"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free Video Maker from Photo — Turn Photos into MP4 Videos

Drop your 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 five vacation photos in JPG format, ask for turn my photos into a slideshow video with music and transitions, 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 — using 5-10 photos gives the best pacing for short social videos.

Matching Input to Actions

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

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

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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.

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 → "turn my photos into a slideshow video with music and transitions" → 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 "turn my photos into a slideshow video with music and transitions" — concrete instructions get better results.

Max file size is 200MB. Stick to JPG, PNG, WEBP, HEIC for the smoothest experience.

Export as MP4 for widest compatibility.