Ai Image To Video Kiss

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

Security Scan

The skill mostly matches its stated purpose (animating photos via a cloud service) but contains a few mismatches in declared requirements and metadata that deserve attention before installing.

Purpose & Capability

The name/description align with the runtime instructions: the skill uploads user images to a cloud rendering backend (nemovideo.ai) and returns MP4s. Requesting a NEMO_TOKEN credential is coherent for a cloud API. However the metadata also declares a config path (~/.config/nemovideo/) that is never referenced in the instructions, which is an unexpected extra scope and may imply reading local config that the runtime text does not describe.

Instruction Scope

SKILL.md instructs the agent to upload user images (potentially sensitive personal photos) and to obtain/store a session token from https://mega-api-prod.nemovideo.ai. All network calls are to that single service and match the described feature set. The agent is told to 'not display raw API responses or token values' which is good. There is no instruction to read other system files or unrelated environment variables, but the presence of an unused config path in metadata is a scope discrepancy worth noting.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by an installer. This is the lowest-risk install model.

Credentials

The skill declares a single primary env var (NEMO_TOKEN), which is appropriate for a cloud API. However, the SKILL.md provides a built-in anonymous-token flow that will fetch a token if NEMO_TOKEN is not set — this conflicts with the registry's 'required env var' claim. The metadata's declared config path (~/.config/nemovideo/) is not used in the instructions, creating an unexplained request for access to a local config location. Both items are inconsistencies the user should be aware of.

Persistence & Privilege

The skill is not always-enabled and is user-invocable; it may store session tokens for the service (normal for a cloud-backed tool). It does not request system-wide privileges or modification of other skills.

What to consider before installing

This skill appears to do what it says: it uploads images to a third‑party rendering service (mega-api-prod.nemovideo.ai) and returns animated MP4s. Before installing, consider: 1) Privacy — you'll be uploading photos (sometimes intimate) to an external service; avoid uploading images you wouldn't want shared and check the service's privacy/retention policy. 2) Credential behavior — although the registry lists NEMO_TOKEN as required, the skill can auto-obtain an anonymous token; decide if you prefer to supply your own token or let it fetch one. 3) Local config path mismatch — the metadata references ~/.config/nemovideo/ but the instructions never use it; review that local path if present and be cautious about granting skill access to local files. 4) Audit network endpoints — all traffic goes to mega-api-prod.nemovideo.ai; if you need stronger guarantees, verify that domain and its privacy/security practices. If these points are acceptable, the skill's actions are proportionate to its purpose; if not, decline or request clarification from the publisher.

Getting Started

Send me your still images and I'll handle the AI video animation. Or just describe what you're after.

Try saying:

• "convert a close-up photo of two people facing each other into a 1080p MP4"
• "animate this image into a short kissing motion video clip"
• "animating romantic still photos into short kiss motion videos for couples, content creators, social media users"

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.

AI Image to Video Kiss — Animate Photos into Kiss Videos

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

Say you have a close-up photo of two people facing each other and want to animate this image into a short kissing motion video clip — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: high-resolution face photos with clear lighting produce the most realistic motion results.

Matching Input to Actions

User prompts referencing ai image to video kiss, 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	ai-image-to-video-kiss
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 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)

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "animate this image into a short kissing motion video clip" — 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.

Common Workflows

Quick edit: Upload → "animate this image into a short kissing motion 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.