Ai Video Maker Free Kiss

create images or clips into romantic video clips with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. couples, wedding content creators use it f...

Security Scan

The skill's behavior mostly matches a cloud video-rendering integration, but there are inconsistencies and privacy risks (automatic anonymous token acquisition, file uploads to an external API, and a metadata/config-path mismatch) that you should understand before installing.

Purpose & Capability

Name/description align with runtime instructions: the SKILL.md describes creating videos from photos/clips via a remote API (upload, render, export). The required NEMO_TOKEN credential and the listed endpoints are coherent with a cloud video service.

Instruction Scope

Instructions explicitly instruct the agent to upload user files (multipart file paths or URLs) and to call remote endpoints that will process media. They also describe generating an anonymous token (UUID + POST) if no NEMO_TOKEN is present, which allows the skill to obtain credentials and transmit user files to the remote service without the user having provided a token. The file-upload examples use local filesystem paths (e.g. files=@/path) which implies the agent may need to access local files; the instructions do not clearly constrain or warn about transmitting sensitive content. Overall the scope is consistent with the stated purpose but carries notable privacy/exfiltration risk and lacks explicit user-consent guidance.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing will be written to disk by an installer. This lowers execution-surface risk. There is no download-from-URL or package install to evaluate.

Credentials

The skill declares a single primary env var (NEMO_TOKEN), which is appropriate for a third-party API. However, the SKILL.md frontmatter metadata also lists a config path (~/.config/nemovideo/) while the registry metadata reports no required config paths — an inconsistency. Also, the skill can obtain an anonymous token automatically, meaning it does not strictly need the user's credential to function; that design increases the chance it will send data to the external service even if the user has not provided credentials.

Persistence & Privilege

always is false and there is no install-time persistence. The skill is user-invocable and allows autonomous invocation (default platform behavior), which is normal; there is no evidence it attempts to modify other skills or system-wide settings.

What to consider before installing

This skill will upload photos and videos you provide to an external service (mega-api-prod.nemovideo.ai) for cloud-based rendering. It will accept either a NEMO_TOKEN you set or obtain an anonymous token on your behalf and then send your media — so it can operate without a user-supplied credential. Before installing or using: 1) Confirm you trust the external domain and understand its privacy/retention policy; avoid uploading sensitive images. 2) Note the SKILL.md includes a config path (~/.config/nemovideo/) even though the registry metadata did not — ask the author whether the skill will read/write that path. 3) If you prefer not to allow automatic anonymous uploads, do not grant NEMO_TOKEN and avoid invoking the skill, or ask the provider to remove the anonymous-token flow. 4) Because this is instruction-only (no code to review), treat it as a remote-service bridge: verify the service's reputation before sending private media.

Getting Started

Got images or clips to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "create two photos of a couple kissing at a wedding into a 1080p MP4"
• "create a short romantic video with music and transitions from these kiss photos"
• "creating free romantic or kiss moment videos from photos for couples, wedding content 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.

AI Video Maker Free Kiss — Create Romantic Videos from Photos

Drop your images or clips 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 two photos of a couple kissing at a wedding, ask for create a short romantic video with music and transitions from these kiss photos, 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 — using 3-5 high-resolution photos gives the smoothest slideshow transitions.

Matching Input to Actions

User prompts referencing ai video maker free 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 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.

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

Header	Value
X-Skill-Source	ai-video-maker-free-kiss
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a short romantic video with music and transitions from these kiss photos" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "create a short romantic video with music and transitions from these kiss 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.