Youtube Photo Video

Skip the learning curve of professional editing software. Describe what you want — turn these photos into a YouTube slideshow video with transitions and musi...

Security Scan

The skill's functionality (upload photos to a cloud rendering backend) is coherent, but there are inconsistencies between the declared metadata and the runtime instructions and the skill asks to upload user images to an external service — review before installing or sending sensitive images.

Purpose & Capability

The skill's stated purpose (turn photos into YouTube-ready videos) aligns with the runtime actions (uploading images, starting render jobs, polling for results). Requiring a NEMO_TOKEN is reasonable for a cloud service, but the SKILL.md provides an anonymous-token flow if NEMO_TOKEN is missing, so declaring NEMO_TOKEN as a required primary credential is inconsistent with the instructions.

Instruction Scope

Instructions explicitly direct the agent to upload user files and send them to a third-party API (https://mega-api-prod.nemovideo.ai). They also instruct generating a UUID, requesting anonymous tokens, creating sessions, uploading files (multipart or URLs), using SSE for interactive edits, and polling render endpoints. These actions are within the advertised purpose, but the SKILL.md also describes deriving X-Skill-Platform from the agent's install path and references a config path (~/.config/nemovideo/), which implies the agent may inspect local file paths and home-directory locations — this expands scope beyond pure upload/render and may read local environment/install location.

Install Mechanism

Instruction-only skill with no install spec or code to write to disk. This is low-risk from install mechanism perspective.

Credentials

Registry metadata lists NEMO_TOKEN as a required primary credential, but SKILL.md provides a fallback anonymous-token acquisition flow (POST to /api/auth/anonymous-token) and thus NEMO_TOKEN may not actually be strictly required. The SKILL.md frontmatter also references a config path (~/.config/nemovideo/) even though the registry summary lists no required config paths — a mismatch. Aside from NEMO_TOKEN, no unrelated credentials are requested. The real risk is that user images and generated session tokens will be sent to the external service; sensitive content could be exposed.

Persistence & Privilege

The skill is not marked always:true and does not request persistent installation or to modify other skills. It does create and use session IDs for render jobs, but that is limited to its own workflow. Autonomous invocation is allowed (default) but not combined with other high-risk factors here.

What to consider before installing

This skill uploads your images and session data to a third-party service (nemovideo.ai). Before installing or using it: 1) Decide whether you are comfortable sending photos (especially sensitive ones) to an external renderer. 2) Note the inconsistency: the registry declares NEMO_TOKEN as required, but the skill can obtain an anonymous token itself — set an environment token only if you trust the service. 3) Ask the publisher for source code or a privacy policy / terms of service for mega-api-prod.nemovideo.ai and confirm data retention and access controls. 4) If you must use it, avoid uploading private or sensitive images and consider creating a throwaway account or using the anonymous flow rather than supplying long-lived credentials.

Getting Started

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

Try saying:

• "turn my images and photos"
• "export 1080p MP4"
• "turn these photos into a YouTube"

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.

YouTube Photo Video — Turn Photos Into YouTube Videos

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

Say you have five YouTube thumbnail photos and want to turn these photos into a YouTube slideshow video with transitions and music — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: fewer photos with longer durations per slide tend to look more professional than rapid slideshows.

Matching Input to Actions

User prompts referencing youtube 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.

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is youtube-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 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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these photos into a YouTube slideshow video with transitions and music" — 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 with YouTube uploads.

Common Workflows

Quick edit: Upload → "turn these photos into a YouTube slideshow video with transitions and music" → 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.