Ai Animation From Image

v1.0.0

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

⭐ 0· 86·0 current·0 all-time

by@vcarolxhberger

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vcarolxhberger/ai-animation-from-image.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Ai Animation From Image" (vcarolxhberger/ai-animation-from-image) from ClawHub.
Skill page: https://clawhub.ai/vcarolxhberger/ai-animation-from-image
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install ai-animation-from-image

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-animation-from-image

Security Scan

VirusTotal

Pending

View report →

OpenClaw

Suspicious

medium confidence

ℹ

Purpose & Capability

The name/description (convert still images to animated videos) align with the runtime instructions (upload images, create sessions, render/export). Requesting a NEMO_TOKEN is proportionate. Minor inconsistency: the SKILL.md frontmatter/metadata references a config path (~/.config/nemovideo/) while the registry record listed no required config paths — this mismatch should be clarified.

✓

Instruction Scope

SKILL.md clearly instructs the agent to upload user media to a remote API, create sessions, use SSE and render endpoints, and optionally obtain an anonymous token when NEMO_TOKEN is absent. The instructions do not direct the agent to read unrelated system files or unrelated secrets. Uploading user media and making network calls to the nemovideo.ai endpoints is expected for this functionality.

✓

Install Mechanism

There is no install spec and no code files (instruction-only). That minimizes local disk/write risk — the skill performs remote API calls rather than installing third-party binaries.

ℹ

Credentials

The skill requires a single credential (NEMO_TOKEN) which is reasonable. It also documents a fallback anonymous-token flow (generates UUID and requests a temporary token), which means the agent will reach out to the external service even without a user-provided token. The frontmatter's configPath mention is not reflected in the registry metadata — check whether the skill expects to read or store files under ~/.config/nemovideo/.

✓

Persistence & Privilege

always is false and the skill is user-invocable. The skill does not request permanent agent-wide presence or modification of other skills. It does cause network activity and remote render jobs (normal for this feature) but does not escalate local privileges.

What to consider before installing

This skill will upload your images/audio to an external rendering service (mega-api-prod.nemovideo.ai) and may create a short-lived anonymous token if you don't provide NEMO_TOKEN. Before installing: 1) Confirm you trust the nemovideo.ai domain or the publisher (no homepage or owner details are provided). 2) Avoid sending sensitive or personally identifiable images unless you accept that they will be processed by that remote service. 3) If you have a NEMO_TOKEN from the service, prefer using it; otherwise anonymous tokens are created automatically and last ~7 days. 4) Ask the author to clarify the config path usage (~/.config/nemovideo/) and why registry metadata omitted it. 5) If you need stronger assurance, request a skill from a known publisher or one with a verifiable homepage/source before granting token access.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎞️ Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk977zj8epfxvgefhahp1fe106x858p62

86downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

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

Try saying:

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

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

Generate a UUID as client identifier
POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Animation from Image — Turn Photos into Animated Videos

Send me your still images and describe the result you want. The AI animation generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a single portrait photo or product image, type "animate this photo with a slow zoom and natural motion", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: high-contrast images with clear subjects produce smoother animations.

Matching Input to Actions

User prompts referencing ai animation from image, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
`/api/tasks/me/with-session/nemo_agent`	POST	Start a new editing session. Body: `{"task_name":"project","language":"<lang>"}`. Returns `session_id`.
`/run_sse`	POST	Send a user message. Body includes `app_name`, `session_id`, `new_message`. Stream response with `Accept: text/event-stream`. Timeout: 15 min.
`/api/upload-video/nemo_agent/me/<sid>`	POST	Upload a file (multipart) or URL.
`/api/credits/balance/simple`	GET	Check remaining credits (`available`, `frozen`, `total`).
`/api/state/nemo_agent/me/<sid>/latest`	GET	Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
`/api/render/proxy/lambda`	POST	Start export. Body: `{"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}`. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-animation-from-image, 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).

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.

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

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.

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

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)

Common Workflows

Quick edit: Upload → "animate this photo with a slow zoom and natural motion" → Download MP4. Takes 20-40 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 slow zoom and natural motion" — 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.

Comments

Loading comments...