Joypix Ai Image To Video

Turn a single product photo or portrait image into 1080p animated video clips just by typing what you need. Whether it's turning static photos into short ani...

Security Scan

The skill's declared purpose (convert images to video) generally matches its runtime instructions, but there are inconsistencies (declared config path in the SKILL.md frontmatter not reflected in registry metadata), and the instructions allow uploading local filesystem paths and creating/using anonymous tokens — behaviors you should understand before trusting it.

Purpose & Capability

Name/description match the actions described (upload image → cloud render → download). The single required credential (NEMO_TOKEN) is appropriate. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this mismatch is unexplained and worth verifying.

Instruction Scope

Runtime instructions direct the agent to call external APIs, create sessions, upload files, and poll render jobs — all expected for a cloud render skill. But the upload instructions explicitly allow multipart uploads from a local path (multipart -F "files=@/path") which implies the agent may read arbitrary local filesystem paths if permitted; that expands scope beyond handling only user-provided images. The instructions also describe anonymous token creation if NEMO_TOKEN is not set, which means the skill can obtain credentials itself without explicit user-provided API keys.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That minimizes disk-write/install risk.

Credentials

The only declared environment credential is NEMO_TOKEN, which is proportional. But the SKILL.md frontmatter also advertises a config path (~/.config/nemovideo/) that the agent might read; the registry metadata earlier listed no config paths — this inconsistency could indicate either sloppy metadata or hidden expectation that the agent can read user config files. Also, the anonymous-token flow lets the skill obtain a runtime token without a user-supplied secret, which is functionally fine but worth noting.

Persistence & Privilege

The skill does not request always:true and does not claim system-wide persistence. It instructs the agent to save session_id for ongoing jobs (normal for session-based APIs) and does not instruct modifying other skills or global agent configuration.

What to consider before installing

This skill is plausible for image→video rendering, but review a few things before installing: 1) The SKILL.md lists a config path (~/.config/nemovideo/) that the registry metadata did not — ask the publisher why and whether the skill will read that folder. 2) The instructions permit uploading files by local path (files=@/path). Only enable the skill if you trust it not to read arbitrary files; avoid granting it broad filesystem access. 3) The skill can mint an anonymous token from https://mega-api-prod.nemovideo.ai if you don't provide NEMO_TOKEN — consider whether you prefer to set your own token or avoid the anonymous flow. 4) There is no homepage or clear publisher identity; verify the service origin and privacy policy before sending sensitive images. If you proceed, provide the minimal-scoped NEMO_TOKEN you can, and do not allow the agent unrestricted access to your file system or other secrets.

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 image into a smooth"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

JoyPix AI Image to Video — Convert Images 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 a single product photo or portrait image, ask for animate this image into a smooth 5-second video clip, and about 30-60 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 animate more smoothly than busy backgrounds.

Matching Input to Actions

User prompts referencing joypix ai image to 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.

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

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

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.

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.

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.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "animate this image into a smooth 5-second video clip" — concrete instructions get better results.

Max file size is 20MB. Stick to JPG, PNG, WEBP, HEIC for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "animate this image into a smooth 5-second video clip" → 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.