Video Generator Kiss Free

Turn two portrait photos of people into 1080p animated kiss videos just by typing what you need. Whether it's generating AI kiss animation clips from photos...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video-generation service: it needs one service token, talks to a single external API, and contains no unrelated credential or install requests.

Purpose & Capability

Name and description (generate kiss animation videos from photos) align with what the SKILL.md requires: an API token (NEMO_TOKEN), session creation, uploads, SSE-based generation, and download of rendered videos. There are no unrelated credentials or binaries requested.

Instruction Scope

Instructions are tightly scoped to session creation, SSE messaging, uploads, state/credits queries, and render/export flows. They do instruct the agent to detect install path (~/.clawhub/ or ~/.cursor/skills/) and to read the skill's YAML frontmatter for attribution headers — this requires checking local paths/files (minor scope creep) but is explained as attribution behavior for the API and appears purposeful.

Install Mechanism

No install spec or code files—instruction-only skill. No downloads or archive extraction are requested, so there is no install-time code execution risk.

Credentials

Only one environment variable (NEMO_TOKEN) is declared as required and used as the bearer token. The skill also supports obtaining an anonymous token via a POST to the nemovideo API if no token is present. This is proportional to the stated cloud-rendering purpose. Users should note that supplying NEMO_TOKEN gives the skill the ability to act on that API account.

Persistence & Privilege

always is false and the skill is user-invocable. There is no requested permanent presence, no modifications of other skills, and no system-wide configuration access beyond optional local path checks for attribution.

Assessment

This skill appears to do what it claims: it sends photos to a remote rendering API and returns a generated video. Before installing, consider: (1) Privacy — your uploaded images will be sent to https://mega-api-prod.nemovideo.ai (or the service it uses); avoid uploading sensitive or identifying photos unless you trust the service and its privacy policy. (2) Token scope — if you set NEMO_TOKEN, the skill can act with that account; only provide a token you control and understand. (3) Local path check — the skill may check a couple of home-folder paths to set an attribution header; this is minor but be aware it touches the filesystem to detect install location. If any of these are unacceptable, do not install or use the skill; otherwise the requested environment access and network calls are proportionate to the stated functionality.

Getting Started

Ready when you are. Drop your images or prompts here or describe what you want to make.

Try saying:

• "generate two portrait photos of people into a 1080p MP4"
• "generate a short romantic kiss animation from these two photos"
• "generating AI kiss animation clips from photos for free for social media creators"

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.

Video Generator Kiss Free — Generate AI Kiss Video Clips

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

A quick example: upload two portrait photos of people, type "generate a short romantic kiss animation from these two photos", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: clear front-facing portrait photos produce the most realistic animations.

Matching Input to Actions

User prompts referencing video generator kiss free, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-generator-kiss-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

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 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 "generate a short romantic kiss animation from these two photos" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a short romantic kiss animation from these two photos" → 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.