Free Ki Video Generation

Get AI generated videos ready to post, without touching a single slider. Upload your text prompts or images (MP4, MOV, JPG, PNG, up to 200MB), say something...

Security Scan

The skill's declared purpose (cloud AI video generation) matches its runtime instructions, but there are small inconsistencies in its metadata and it will upload user files and obtain/hold tokens for an external service of unknown provenance — so proceed cautiously.

Purpose & Capability

Name/description map to the actions in SKILL.md: it calls a cloud video-rendering API, uploads files, creates sessions, polls render status and returns downloadable MP4s. The single declared credential (NEMO_TOKEN) and the listed config path (~/.config/nemovideo/) are consistent with a cloud video service.

Instruction Scope

Instructions explicitly direct the agent to make network calls to https://mega-api-prod.nemovideo.ai, upload user files (up to 200MB), create sessions, poll SSE endpoints, and include attribution headers. These actions are expected for a cloud video service. Minor scope issues: the skill both lists NEMO_TOKEN as required AND documents an anonymous-token flow (so the env var is optional in practice), and it asks to auto-detect platform from the install path (which implies inspecting runtime/install paths). The agent will send user content and metadata to a third-party endpoint — this is functional but important for privacy/security consideration.

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 install risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as the primaryEnv, which is proportionate for an API-backed video service. However, the SKILL.md documents an anonymous-token acquisition flow if NEMO_TOKEN is absent (so the token is not strictly required), and the frontmatter mentions a config path (~/.config/nemovideo/) that the instructions don't clearly require reading. These minor mismatches reduce clarity but are not necessarily malicious.

Persistence & Privilege

always is false and the skill does not request system-wide configuration changes or persistent elevated privileges. Autonomous invocation (disable-model-invocation=false) is the default platform behavior and is not by itself flagged.

What to consider before installing

This skill appears to do what it says (cloud AI video generation) and requires only one API token, but it will upload whatever files you provide to an external domain (mega-api-prod.nemovideo.ai) and can create anonymous tokens on your behalf. Before installing or using it: 1) consider the sensitivity of any media/text you upload — do not upload private/personal/confidential files to an unvetted third party; 2) prefer using the anonymous token flow for untrusted environments rather than placing long-lived secrets in your environment; 3) note the skill has no homepage or public source listed and an unknown owner — if you need stronger assurance, ask the publisher for privacy/security documentation or test with non-sensitive content first; 4) review any usage limits or billing/terms that could affect you (the skill references subscription/credits behavior); 5) if you want higher assurance, request the service domain, a privacy policy, and source or vendor identity before providing real data.

Getting Started

Share your text prompts or images and I'll get started on AI video generation. Or just tell me what you're thinking.

Try saying:

• "generate my text prompts or images"
• "export 1080p MP4"
• "generate a 30-second video from my"

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.

Free AI Video Generation — Generate Videos from Text or Images

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

Say you have a short text description of a product launch scene and want to generate a 30-second video from my product description with background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter and more specific prompts tend to produce better results faster.

Matching Input to Actions

User prompts referencing free ki video generation, 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	free-ki-video-generation
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 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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second video from my product description with background music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "generate a 30-second video from my product description with background music" → Download MP4. Takes 1-2 minutes 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.