Video Maker With Photos Free

Get photo slideshow video ready to post, without touching a single slider. Upload your photos and images (JPG, PNG, WEBP, HEIC, up to 200MB), say something l...

Security Scan

The skill's requirements and runtime instructions are largely consistent with a photo→video cloud rendering service, but review privacy and the declared credential handling before installing.

Purpose & Capability

Name/description (turn photos into videos) match the API endpoints and actions described (session, upload, render). Small inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) but the registry metadata shown above lists no required config paths — this is likely minor metadata drift but worth noting.

Instruction Scope

SKILL.md instructs only to connect to the nemovideo API, create sessions, upload image files, stream SSE events, poll export status, and return download URLs. It does not instruct reading unrelated local files or other environment variables. Important operational behavior: user image files and any metadata are uploaded to a remote domain (mega-api-prod.nemovideo.ai).

Install Mechanism

Instruction-only skill (no install spec, no code files). This is the lowest-risk install pattern because nothing is written to disk by an installer.

Credentials

The only declared required env var is NEMO_TOKEN (primary credential), which is appropriate for an API-backed service. SKILL.md, however, can obtain an anonymous short-lived token if NEMO_TOKEN is absent, so listing NEMO_TOKEN as strictly required is slightly inconsistent. Bearer tokens grant API-level access—do not reuse sensitive credentials from other services.

Persistence & Privilege

always:false and normal agent invocation; the skill does not request permanent/always-on privileges or modification of other skills' configs.

Assessment

This skill appears to be a straightforward front-end for a third‑party cloud video service and will upload any photos you give it to mega-api-prod.nemovideo.ai for server-side rendering. Before installing, consider: 1) Privacy — your images and any captions are sent to an external service; review their privacy/terms and avoid uploading sensitive content. 2) Credentials — NEMO_TOKEN (a Bearer token) grants API access; only provide a token you control and do not reuse credentials from other services. The skill can request a temporary anonymous token itself, so supplying a token is optional in practice; check why the registry declares it required. 3) Trust & provenance — the skill's source/homepage is unknown; if this matters, verify the service operator or prefer a skill from a known publisher. 4) Billing/credits — the instructions mention credits and anonymous tokens with limited credits/expiry; confirm any paid usage before submitting many or large files. If you want a stronger assessment, provide the skill publisher's homepage or the service privacy policy so I can check domain reputation and data retention practices.

Getting Started

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

Try saying:

• "turn my photos and images"
• "export 1080p MP4"
• "turn these 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.

Video Maker With Photos Free — Turn Photos Into Shareable Videos

Send me your photos and images 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 eight vacation photos in JPG format, type "turn these photos into a slideshow video with music and transitions", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using 10 or fewer photos keeps processing fast and the video concise.

Matching Input to Actions

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

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	video-maker-with-photos-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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)

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 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 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 across social platforms and devices.

Common Workflows

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