Ai Video Editor Kiss Free

edit video clips into edited romantic clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. TikTok creators use it for editing kiss or rom...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video-editing integration: it only requires a single service token, uploads user video files to the stated API, and has no install or unrelated credential demands.

Purpose & Capability

Name/description (cloud video editing for romantic/kiss scenes) align with required env var (NEMO_TOKEN) and the SKILL.md which documents an external Nemovideo API. Declared config path (~/.config/nemovideo/) and primaryEnv (NEMO_TOKEN) are plausible for this purpose.

Instruction Scope

Instructions require uploading user-supplied media and exchanging tokens with https://mega-api-prod.nemovideo.ai, saving session_id, and streaming SSE chat. These are expected for a cloud render service but do mean user videos (and session metadata) will be transmitted to that external endpoint. The skill does read its own frontmatter and may probe install-paths to set an X-Skill-Platform header — this is limited but should be noted as filesystem access.

Install Mechanism

No install spec or code is included (instruction-only), so nothing is written to disk or downloaded by default. Lowest install risk.

Credentials

Only NEMO_TOKEN is required (primary credential). That is proportionate to a service that requires API authentication. No unrelated secrets or multiple credentials are requested.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request permanent platform-wide privileges or modify other skills. It does instruct saving session_id and using tokens for API calls, which is standard for a client of a remote service.

Assessment

This skill appears to do what it says: it will upload your video files to an external Nemovideo API and use a single service token (NEMO_TOKEN) or create an anonymous token if none is provided. Before installing/using it, confirm you are comfortable uploading potentially sensitive videos to https://mega-api-prod.nemovideo.ai (the skill's source and homepage are unknown), check service privacy/retention and cost implications (credits/exports may require registration), and avoid supplying unrelated credentials. If you plan to provide a long-lived NEMO_TOKEN, ensure it’s scoped appropriately and can be revoked.

Getting Started

Send me your video clips and I'll handle the AI kiss scene editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute romantic short film clip into a 1080p MP4"
• "detect and trim the kiss scene, add smooth transitions and background music"
• "editing kiss or romantic scenes from video footage automatically for TikTok creators"

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.

AI Video Editor Kiss Free — Edit Romantic Scenes Into Clips

Drop your video clips in the chat and tell me what you need. I'll handle the AI kiss scene editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute romantic short film clip, ask for detect and trim the kiss scene, add smooth transitions and background music, 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 — shorter clips under 60 seconds process significantly faster and give cleaner AI scene detection.

Matching Input to Actions

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

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.

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

• X-Skill-Source: ai-video-editor-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.

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)

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.

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

Common Workflows

Quick edit: Upload → "detect and trim the kiss scene, add smooth transitions and background music" → 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 "detect and trim the kiss scene, add smooth transitions and background music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.