Free Video Generation Kling

Skip the learning curve of professional editing software. Describe what you want — generate a 5-second video of a sunset over the ocean from a text descripti...

Security Scan

The skill's requirements and runtime instructions are coherent with a remote AI video-generation service: it needs a NEMO_TOKEN, talks only to nemovideo endpoints, and has no installable code or unrelated credentials.

Purpose & Capability

The skill claims to generate videos via a remote backend and only requests a single service token (NEMO_TOKEN) and an optional config path (~/.config/nemovideo/) consistent with that purpose. No unrelated service credentials or binaries are requested.

Instruction Scope

The SKILL.md fully describes API calls for auth, session creation, upload, SSE chat, and export — all scoped to the stated backend (mega-api-prod.nemovideo.ai). Two items to note: (1) if NEMO_TOKEN is missing the instructions say to obtain an anonymous token automatically by POSTing to the backend, and (2) it instructs the agent not to display raw API responses or token values to the user. Both behaviors can be legitimate but reduce user visibility into credential creation and storage.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is downloaded or written by an installer as part of skill installation.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which is appropriate for a hosted video service. However the skill also auto-provisions an anonymous NEMO_TOKEN if not present and expects to persist session_id/token (metadata references a config path). This automatic token creation and likely storage is functionally reasonable but worth user awareness.

Persistence & Privilege

The skill does not request always: true or system-wide privileges. It suggests storing session state/token (typical for remote service sessions) but does not modify other skills or global agent settings.

Assessment

This skill is coherent with its stated purpose but it will send your prompts and any uploaded media to mega-api-prod.nemovideo.ai and may create and store an anonymous NEMO_TOKEN/session_id if you haven't provided one. Before installing or using it, consider: (1) whether you are comfortable uploading the media you plan to generate/edit to that external service; (2) whether you prefer to provide your own NEMO_TOKEN (so the skill won't mint one automatically); (3) where the skill will store the token/session (it references ~/.config/nemovideo/) and whether you want those files on disk; and (4) reviewing the service's privacy/retention policy. If you want, I can: (A) extract the exact HTTP request examples from the SKILL.md so you can review them, or (B) draft a short user-facing consent message to surface that an anonymous token will be created and stored.

Getting Started

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

Try saying:

• "generate a short text prompt describing a scene into a 1080p MP4"
• "generate a 5-second video of a sunset over the ocean from a text description"
• "generating short AI videos from text or image prompts for free for content creators, social media users, marketers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free Video Generation Kling — Generate AI Videos from Prompts

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

A quick example: upload a short text prompt describing a scene, type "generate a 5-second video of a sunset over the ocean from a text description", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.

Worth noting: shorter prompts with clear motion descriptions produce more consistent results.

Matching Input to Actions

User prompts referencing free video generation kling, 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: free-video-generation-kling
• 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)

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

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.

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

Common Workflows

Quick edit: Upload → "generate a 5-second video of a sunset over the ocean from a text description" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 5-second video of a sunset over the ocean from a text description" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.