Photo Maker

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 mostly does what it says (upload photos to a cloud renderer) but there are small inconsistencies and a few runtime behaviors you should be aware of before installing — notably automatic token generation, filesystem probing for install/config paths, and uploading user images to an external API.

Purpose & Capability

The name/description (turn photos into videos) aligns with the instructions: calls to a cloud render API, upload endpoints, export and status endpoints, and a single service token (NEMO_TOKEN) are expected for this purpose.

Instruction Scope

The SKILL.md instructs the agent to upload user files and exchange SSE messages with the external API — expected. It also instructs the agent to read this file's YAML frontmatter and to detect the agent install path (~/.clawhub/, ~/.cursor/skills/) at runtime to set an X-Skill-Platform header. That file-system probing is not strictly necessary for core function and expands the skill's runtime scope (it may require reading agent paths). The doc also contains an automated anonymous-token flow (POST to /api/auth/anonymous-token) if NEMO_TOKEN is absent, which will cause outbound network traffic and issuance/storage of short-lived tokens.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only. This minimizes install-time risk because nothing is downloaded or written by an installer.

Credentials

Declared primary credential is NEMO_TOKEN which is proportionate to a cloud rendering service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and instructs reading install paths for platform detection; the registry metadata summary provided earlier said 'Required config paths: none'. This mismatch (declared vs. frontmatter) is an inconsistency to clarify. Otherwise the skill does not request unrelated credentials.

Persistence & Privilege

always:false (default) and no install-time persistence is requested. The skill does not request to modify other skills or system-wide agent settings. It will, however, create session state on the remote service and may store short-lived tokens client-side during the session, per the anonymous-token flow described.

What to consider before installing

What to consider before installing: - This skill uploads your photos to a third-party service (mega-api-prod.nemovideo.ai). Do not use it for private or sensitive images unless you trust the service and its retention/privacy policies. - You can supply your own NEMO_TOKEN (preferred). If you don't, the skill will automatically request an anonymous token on your behalf (100 free credits, 7-day expiry), which creates network traffic to that API and results in a short-lived credential being used. - The skill's instructions tell the agent to probe certain filesystem locations to detect the platform and to read the skill's YAML frontmatter; this is not essential for core functionality and expands the set of files the agent will examine. If you want to limit file access, ask for clarification or deny filesystem probing. - There is a metadata inconsistency: the registry summary lists no required config paths but the SKILL.md frontmatter references ~/.config/nemovideo/. Ask the author to confirm whether the skill needs access to that path. - If you decide to use it, prefer creating/using an account token you control (NEMO_TOKEN) rather than relying on anonymous token generation, and verify the service's privacy/retention policy for uploaded media. If you need higher assurance, request source or a vetted official integration before sending sensitive material.

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"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Photo Maker — Turn Photos Into Videos

This tool takes your images 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 in JPG format and want to turn my photos into a slideshow video with music and transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using 10 or fewer photos keeps the output tight and under a minute.

Matching Input to Actions

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

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

• X-Skill-Source: photo-maker
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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.

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

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)

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

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.