Beginners Photo Video

Turn five vacation photos from your phone into 1080p slideshow video clips just by typing what you need. Whether it's turning a set of photos into a shareabl...

Security Scan

The skill's stated purpose (turn phone photos into short videos) is plausible and most requirements line up, but there are several inconsistencies and small scope-creep items you should understand before installing.

Purpose & Capability

The skill claims to convert photos to 1080p videos using a cloud backend; the required credential (NEMO_TOKEN) and the API endpoints in SKILL.md match that purpose. However, SKILL.md metadata mentions a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — an inconsistency in declared requirements. Also the skill derives attribution headers from the agent's install path, which requires probing the environment; this is not obviously necessary for basic photo-to-video functionality.

Instruction Scope

The SKILL.md contains concrete runtime instructions that include: checking the NEMO_TOKEN env var, falling back to POSTing to an anonymous-token endpoint to obtain a token, creating sessions, uploading files (multipart or via URL), and using SSE and polling the render endpoint. These network actions are coherent with the service, but the instructions also require determining the agent's install path to set X-Skill-Platform and imply access to local file paths for multipart uploads. That means the agent may read filesystem paths (install path and any user-specified file paths) which is broader than the skill's declared requirements and should be disclosed to users.

Install Mechanism

There is no install spec and no code files — SKILL.md is instruction-only. That minimizes write-to-disk risk. Network calls described in the instructions are the main runtime surface.

Credentials

Only one credential is declared (NEMO_TOKEN) and it is directly used by the API calls described, which is proportionate. The skill will create an anonymous token if none exists (via the public anonymous-token endpoint). Still, the SKILL.md metadata lists a config path (~/.config/nemovideo/) while the top-level registry reported none; this mismatch should be clarified. Also the skill tells the agent to keep session tokens for operations — make sure tokens are stored securely and not leaked.

Persistence & Privilege

always is false and the skill does not request persistent system privileges. It does instruct the agent to keep session IDs and tokens for the duration of the session, which is normal for a cloud service client. There is no instruction to modify other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says (upload images to nemovideo.ai and return a short video) but has some implementation oddities. Before installing: 1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and read its privacy/terms — your photos will be uploaded to that backend. 2) Ask the publisher to resolve the metadata mismatch (SKILL.md lists a config path while registry metadata does not) and to explain why the skill needs to probe the agent's install path to set headers. 3) Test with non-sensitive images first and ensure tokens can be revoked/rotated (anonymous tokens are time-limited but confirm). 4) If you are concerned about local-file access, verify where the agent will read files from and whether uploads are initiated only for files you explicitly drop in chat. If you want higher assurance, request the skill publisher or maintainer contact info or a homepage before using it with private material.

Getting Started

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

Try saying:

• "turn five vacation photos from your phone into a 1080p MP4"
• "turn my photos into a short video with music and transitions"
• "turning a set of photos into a shareable video for beginners and casual creators"

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.

Beginners Photo Video — Turn Photos Into Shareable Videos

Drop your photos or 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 from your phone, ask for turn my photos into a short 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 a short video.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is beginners-photo-video, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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.

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

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

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.

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

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

Export as MP4 for widest compatibility.