Image To Video Effects

convert still images into animated video clips with this skill. Works with JPG, PNG, WEBP, HEIC files up to 200MB. social media creators use it for turning s...

Security Scan

The skill's stated purpose (animating photos via a cloud rendering API) matches its instructions and requested credential, but there are a few small inconsistencies and privacy-relevant behaviors you should be aware of before installing.

Purpose & Capability

The name/description match the runtime instructions: the skill uploads images and drives a cloud API (mega-api-prod.nemovideo.ai) to render videos and returns download URLs. Requiring a NEMO_TOKEN is coherent for this cloud service. Minor inconsistency: the registry metadata earlier listed no required config paths, but the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) — this isn't necessary for the described functionality and is unexpected.

Instruction Scope

SKILL.md gives explicit procedural instructions for creating sessions, uploading files, long-polling SSE, and exporting — all within the declared purpose. It also instructs that if NEMO_TOKEN is absent the agent should POST to an anonymous-token endpoint and extract data.token for use; that behavior is functional but notable because it lets the skill obtain usable credentials automatically. The skill does not instruct reading other unrelated system files, but the declared config path in frontmatter is surprising.

Install Mechanism

No install spec and no code files (instruction-only). This is lowest-risk from an installation perspective — nothing is downloaded or written by the skill itself per the package.

Credentials

Only one credential (NEMO_TOKEN) is declared as required and is appropriate for a cloud rendering service. However, the skill is allowed to mint an anonymous token on first use by calling the service's auth endpoint, which means it can operate without a pre-provided user token. The frontmatter's configPaths entry (~/ .config/nemovideo/) appears unnecessary and is not reflected in the registry metadata — that mismatch reduces confidence that environment/config needs are cleanly declared.

Persistence & Privilege

always is false and the skill does not request elevated or persistent platform privileges. It does not instruct changing other skills or system-wide agent settings.

Assessment

This skill routes uploaded images to a third-party cloud API (mega-api-prod.nemovideo.ai) to produce videos. It legitimately needs a NEMO_TOKEN but will automatically request an anonymous token if one isn't present — so it can operate without you providing secrets. Before installing, consider: (1) Do you trust the destination service with the images you will upload (privacy/sensitivity)? (2) Confirm the API host/domain and headers match what you expect; the skill requires custom attribution headers which may be used for billing/attribution. (3) The SKILL.md and registry disagree about a config path (~/.config/nemovideo/) — ask the publisher why that path is declared and whether the skill will read or write files there. (4) Check service terms/pricing (anonymous tokens have limited credits). If you plan to process sensitive images or need tighter control over credentials, avoid or audit further; otherwise the skill appears internally consistent with its stated purpose.

Getting Started

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

Try saying:

• "convert my still images"
• "export 1080p MP4"
• "animate this photo with a zoom"

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.

Image to Video Effects — Animate Photos Into Video Clips

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

Say you have three landscape photos or a single product shot and want to animate this photo with a zoom and pan effect and export as a video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: high-contrast images with clear subjects produce the most noticeable motion effects.

Matching Input to Actions

User prompts referencing image to video effects, 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	image-to-video-effects
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.

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)

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

Common Workflows

Quick edit: Upload → "animate this photo with a zoom and pan effect and export as a video" → 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 "animate this photo with a zoom and pan effect and export as a video" — 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 all social platforms.