← Back to Skills Marketplace
linmillsd7

Ai Image To Video Making

by linmillsd7 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
72
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install ai-image-to-video-making
Description
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...
README (SKILL.md)

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"
  • "turn these images into a 15-second"

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 Image to Video Making — Convert Images Into Videos

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

A quick example: upload three product photos in JPG format, type "turn these images into a 15-second video with smooth transitions", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using fewer images per video speeds up processing noticeably.

Matching Input to Actions

User prompts referencing ai image to video making, 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":"\x3Clang>"}. 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/\x3Csid> POST Upload a file (multipart) or URL.
/api/credits/balance/simple GET Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/\x3Csid>/latest GET Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda POST Start export. Body: {"id":"render_\x3Cts>","sessionId":"\x3Csid>","draft":\x3Cjson>,"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.

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

Header Value
X-Skill-Source ai-image-to-video-making
X-Skill-Version frontmatter version
X-Skill-Platform auto-detect: clawhub / cursor / unknown from install path

All requests must include: Authorization: Bearer \x3CNEMO_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=\x3Cid> (get \x3Cid> 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 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)

Common Workflows

Quick edit: Upload → "turn these images into a 15-second video with smooth 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these images into a 15-second video with smooth 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.

Usage Guidance
This skill appears to be what it claims: it will upload images and use a remote NemoVideo API to render videos. Before installing or running it, consider: (1) privacy — your images will be sent to https://mega-api-prod.nemovideo.ai; don't send sensitive images unless you trust that service; (2) token scope — if you set NEMO_TOKEN as an environment variable, treat it like a password (it authorizes API actions); prefer using an anonymous token or a limited-scope token if available; (3) metadata mismatch — SKILL.md mentions a config path (~/.config/nemovideo/) even though registry metadata didn't list it; verify whether the agent will read that directory if you care about local config exposure; (4) network monitoring — the skill relies entirely on HTTP calls, so review logs or network policies if you need to restrict outbound access. If any of these are unacceptable, do not install or provide a persistent NEMO_TOKEN.
Capability Analysis
Type: OpenClaw Skill Name: ai-image-to-video-making Version: 1.0.0 The skill bundle provides a legitimate integration for an AI image-to-video generation service hosted at nemovideo.ai. It includes detailed instructions for the agent to handle authentication (via NEMO_TOKEN or an anonymous fallback), session management, and file uploads. The behavior is consistent with the stated purpose of converting images to video, and no indicators of data exfiltration, malicious execution, or harmful prompt injection were found in SKILL.md or _meta.json.
Capability Assessment
Purpose & Capability
Name/description describe a remote image→video service and the SKILL.md exclusively documents calling an external NemoVideo API, uploading files, and rendering. Requesting a single API token (NEMO_TOKEN) is appropriate for this service integration.
Instruction Scope
Instructions direct the agent to read NEMO_TOKEN (if present), otherwise obtain an anonymous token by POSTing to the service, create a session, upload media, stream SSE events, and poll status — all consistent with a cloud-render workflow. They do not ask the agent to read arbitrary user files or unrelated environment variables. One small scope mismatch: the skill frontmatter (in SKILL.md metadata) lists a config path (~/.config/nemovideo/), but the registry metadata provided to you listed no required config paths; the SKILL.md does not explicitly instruct reading that directory, so this is likely minor metadata drift.
Install Mechanism
Instruction-only skill with no install steps and no downloaded code. This minimizes on-disk risk — all runtime actions are HTTP requests to the remote API.
Credentials
Only one credential (NEMO_TOKEN) is declared as primary and is used for API authorization. The skill can fall back to requesting an anonymous token from the service if no env var is set, which is reasonable for a public/free-tier workflow. No unrelated secrets or multiple credentials are requested.
Persistence & Privilege
always is false and the skill does not request persistent system privileges or attempt to modify other skills or system settings. It only creates ephemeral sessions on the remote service.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install ai-image-to-video-making
  3. After installation, invoke the skill by name or use /ai-image-to-video-making
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
AI Image to Video Making — Initial Release - Instantly convert uploaded still images (JPG, PNG, WEBP, HEIC, up to 200MB) into 1080p MP4 videos with AI-powered transitions and animation. - No manual editing required—just describe the video you want and get a ready-to-post video in under a minute. - Fully cloud-based processing—no installation needed; videos are rendered on remote GPU servers. - Supports multiple user workflows: quick edits, batch processing, and step-by-step refinements, all while preserving your project session. - Simple onboarding with automatic anonymous authentication if no token is provided, and clear handling of uploads, credits, and exports. - Action-oriented chat flow: just upload images and describe your goal to begin.
Metadata
Slug ai-image-to-video-making
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Ai Image To Video Making?

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... It is an AI Agent Skill for Claude Code / OpenClaw, with 72 downloads so far.

How do I install Ai Image To Video Making?

Run "/install ai-image-to-video-making" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Ai Image To Video Making free?

Yes, Ai Image To Video Making is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Ai Image To Video Making support?

Ai Image To Video Making is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Ai Image To Video Making?

It is built and maintained by linmillsd7 (@linmillsd7); the current version is v1.0.0.

💬 Comments