Free Kling Ai Video Generation

generate text prompts or images into AI-generated video clips with this skill. Works with JPG, PNG, WEBP, MP4 files up to 20MB. content creators, social medi...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud video-generation integration: it only asks for a single API token and describes API calls needed to upload assets, create sessions, and render video — nothing appears to be unrelated to its stated purpose.

Purpose & Capability

Name/description map to an external video-generation API. Requesting NEMO_TOKEN as the primary credential is appropriate for a hosted service. The declared config path (~/.config/nemovideo/) is plausible for storing session/token data but is not required by the core described workflow (minor mismatch).

Instruction Scope

SKILL.md instructs the agent to call nemovideo.ai endpoints, upload user-provided files, create sessions, poll SSE, and return download URLs — all expected for a video render skill. It does not instruct reading arbitrary system files or unrelated environment variables. Slight scope ambiguity: it references auto-detecting install path (for X-Skill-Platform) and saving session_id but doesn't specify how/where to persist session data; frontmatter lists a config path that the runtime instructions never explicitly read.

Install Mechanism

No install steps or external downloads — instruction-only, which minimizes on-disk installation risk.

Credentials

Only one credential (NEMO_TOKEN) is required and is the documented bearer token for API calls. That is proportionate. The presence of a declared config path is slightly more access than strictly necessary but not uncommon for storing tokens/sessions.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill does not request persistent system-wide privileges or modifications to other skills. Autonomous invocation combined with external network access increases potential blast radius, but this is expected for an integration skill.

Assessment

This skill appears to be a straightforward integration with an external video-generation API. Before enabling it: only provide a NEMO_TOKEN you trust (avoid reusing high-privilege credentials), do not upload sensitive personal files or secrets as assets, and be aware the skill will make network requests to mega-api-prod.nemovideo.ai and may store session-related values (session_id / ephemeral tokens). The frontmatter's config path and the 'auto-detect install path' note are minor mismatches — they imply the skill might expect to persist data locally; ask the author how/where session tokens are stored if you need stronger guarantees. If you do not trust the remote service, do not enable autonomous invocation or do not install the skill.

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 5-second cinematic video clip"

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.

Free Kling AI Video Generation — Generate AI Videos From Prompts

Drop your text prompts or images in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short text description like 'a fox running through a snowy forest at dusk', ask for generate a 5-second cinematic video clip from my text prompt using Kling AI, and about 1-3 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter prompts with clear motion descriptions tend to produce more consistent results.

Matching Input to Actions

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

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

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 5-second cinematic video clip from my text prompt using Kling AI" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and video editors.

Common Workflows

Quick edit: Upload → "generate a 5-second cinematic video clip from my text prompt using Kling AI" → Download MP4. Takes 1-3 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.