Photo Video Best

Turn ten vacation photos in JPG format into 1080p polished photo videos just by typing what you need. Whether it's turning photo collections into shareable v...

Security Scan

The skill's requirements and runtime instructions align with its stated purpose (uploading photos to a cloud renderer using a NemoVideo token); nothing requested appears disproportionate or unrelated.

Purpose & Capability

The skill claims to convert photos into videos and only requires a NEMO_TOKEN and a Nemo config path; those map directly to a cloud rendering backend (nemovideo.ai) referenced throughout SKILL.md, so requested credentials and config appear appropriate for the stated purpose.

Instruction Scope

The instructions are narrowly scoped to: check/obtain NEMO_TOKEN (anonymous token flow), create a session, upload files or URLs, use SSE for generation, poll render status, and return download URLs. They do not direct the agent to read unrelated local files or other environment variables, nor to exfiltrate data to unknown endpoints beyond the declared API host.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk or fetched at install time. That minimizes install-time risk.

Credentials

Only one environment variable (NEMO_TOKEN) is required and it is the primary credential used for Bearer auth to the service the skill integrates with. No unrelated secrets or broad system credentials are requested.

Persistence & Privilege

The skill is not marked always:true and does not request persistent or system-wide configuration changes. It relies on per-session tokens and normal API calls and does not claim to modify other skills or global agent settings.

Assessment

This skill uploads your photos to a third‑party cloud service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN for authorization. Before installing or using it: (1) confirm you trust nemovideo.ai and read its privacy/terms regarding uploaded media; (2) avoid uploading sensitive photos you wouldn't want stored or processed off-device; (3) prefer using the anonymous token flow described (temporary token) rather than placing long‑lived credentials in environment variables; (4) if you set NEMO_TOKEN, treat it as a secret and remove/revoke it after use; and (5) if you need certainty about how long the service retains media or tokens, ask the provider or test with non-sensitive content first.

Getting Started

Ready when you are. Drop your photos and images here or describe what you want to make.

Try saying:

• "turn ten vacation photos in JPG format into a 1080p MP4"
• "turn my photos into a slideshow video with music and transitions"
• "turning photo collections into shareable videos for social media 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.

Photo Video Best — Turn Photos Into Polished Videos

This tool takes your photos and images and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have ten vacation 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: fewer than 20 photos process the fastest and keep the video tight.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	photo-video-best
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.

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.

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

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, HEIC, WEBP 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.