Picture To Video Ai

Get animated video clips ready to post, without touching a single slider. Upload your still images (JPG, PNG, WEBP, HEIC, up to 200MB), say something like "t...

Security Scan

The skill's instructions, required credential, and network endpoints align with a photo→video cloud-rendering service, but there are minor metadata inconsistencies and privacy/provenance considerations you should review before installing.

Purpose & Capability

The name/description (convert photos to short videos) match the runtime instructions (upload images, call mega-api-prod.nemovideo.ai render endpoints). Requesting a single service token (NEMO_TOKEN) is proportionate. Minor inconsistency: the registry metadata in the package summary lists no required config paths, but the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/). That mismatch should be clarified (is the skill expected to read/write that local config?).

Instruction Scope

SKILL.md explicitly directs the agent to upload user images and interact with the nemovideo.ai API (auth, upload, SSE chat, export polling). Those actions are within scope for a cloud-rendering photo→video skill. It does instruct automatic anonymous-token acquisition if NEMO_TOKEN is absent and to 'store session_id' for subsequent calls — storing session state is expected, but the document doesn't specify storage scope or retention. The instructions are specific about endpoints and headers and do not ask the agent to read unrelated files or secrets.

Install Mechanism

No install spec and no code files — instruction-only. This is the lowest install risk (nothing is written to disk by an installer).

Credentials

Only NEMO_TOKEN is declared as required/primary, which is appropriate for an API-backed renderer. The SKILL.md includes logic to generate an anonymous token if NEMO_TOKEN is not present (reasonable). The SKILL.md frontmatter also references a local config path (~/.config/nemovideo/), but the registry listing did not declare config paths — either the skill intends to persist session state locally (plausible) or the metadata is inconsistent. No unrelated credentials are requested.

Persistence & Privilege

always:false (default) and autonomous invocation enabled (normal). The skill will contact an external cloud service and may retain session IDs/tokens for the session; this is expected for its function. There is no request to modify other skills or global agent settings.

Assessment

This skill appears to do what it says: it uploads your images to nemovideo.ai and returns rendered MP4s. Before installing, consider: (1) provenance — the skill source/homepage is unknown, so you cannot audit the backend or operator; (2) privacy — your images will be sent to https://mega-api-prod.nemovideo.ai (verify you are comfortable with that service's privacy and retention policies, and avoid uploading sensitive images); (3) tokens/session storage — the skill will request or create a NEMO_TOKEN and store a session_id for renders (clarify where/how that is stored and for how long); (4) credits/cost — anonymous tokens are described as time-limited/credit-limited — check whether exports can incur charges; (5) metadata mismatch — ask the publisher to clarify the configPath declaration (~/.config/nemovideo/) vs. registry metadata. If any of these are unacceptable or unclear, do not install or only use with non-sensitive test images.

Getting Started

Got still images to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "convert three product photos or a single portrait image into a 1080p MP4"
• "turn my photos into a smooth animated video with transitions"
• "converting still photos into shareable video content for social media creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Picture to Video AI — Convert Photos into Video Clips

Drop your still 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 three product photos or a single portrait image, ask for turn my photos into a smooth animated video with transitions, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — high-contrast images with clear subjects produce the most natural-looking motion.

Matching Input to Actions

User prompts referencing picture to video ai, 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	picture-to-video-ai
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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.

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

Common Workflows

Quick edit: Upload → "turn my photos into a smooth animated video with transitions" → Download MP4. Takes 30-90 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 smooth animated video with 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.