Free Video Generation China

Turn a text prompt describing a mountain landscape scene into 1080p AI generated videos just by typing what you need. Whether it's generating short videos fr...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud video-generation integration, but there are a few small mismatches (declared config paths vs registry, filesystem/install-path checks, and automatic anonymous token provisioning) you should be aware of before installing.

Purpose & Capability

The skill is a cloud video-generation frontend and only requests a single service credential (NEMO_TOKEN) that matches that purpose. No unrelated binaries or extra credentials are requested. One inconsistency: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths.

Instruction Scope

Runtime instructions are focused on creating a session, uploading media, sending messages via SSE, polling renders, and returning download URLs — all consistent with a video API. However, the instructions also tell the agent to: (1) read YAML frontmatter and detect the agent's install path to set attribution headers (requires filesystem/installation-path access), and (2) upload arbitrary local files when the user provides them. These filesystem and install-path reads go slightly beyond a purely API-only integration and aren’t reflected in the registry metadata.

Install Mechanism

This is an instruction-only skill with no install spec or downloadable code, so nothing is written to disk by an installer. That is the lowest-risk install model.

Credentials

The skill requests a single credential (NEMO_TOKEN) which is proportionate for a cloud API integration. It will also automatically obtain an anonymous token from https://mega-api-prod.nemovideo.ai if NEMO_TOKEN is absent — this behavior is reasonable but worth noting because it involves network calls to provision temporary credentials and may result in the agent holding/storing a token for future calls.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide privileges. It does instruct the agent to use session tokens and mentions a config directory in the frontmatter; the SKILL.md does not explicitly instruct persisting tokens to disk, but the combination of configPaths in the frontmatter and filesystem reads suggests the agent might read or write local config if implemented. This is not an elevated privilege by itself, but verify where tokens are stored.

Assessment

This skill appears to do what it says: call a cloud video API, create sessions, upload files, and return download URLs. Before installing: (1) confirm you trust the domain mega-api-prod.nemovideo.ai and review its privacy/terms, (2) be aware the skill will try to auto-provision an anonymous NEMO_TOKEN if none is provided (it makes a network POST and receives a temporary token), (3) note the skill may read its own SKILL.md frontmatter and check install/config paths (it references ~/.config/nemovideo/ and install-path detection) — if you’re uncomfortable with filesystem access, avoid installing or restrict the agent’s filesystem permissions, (4) do not provide sensitive files unless you understand how uploads are used, and (5) monitor network activity and any stored tokens after first use. If you want higher assurance, ask the skill author to clarify where (if anywhere) tokens are persisted and to remove any unnecessary filesystem/install-path checks.

Getting Started

Got text prompts 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 text prompt describing a mountain landscape scene into a 1080p MP4"
• "generate a 15-second video clip from my product description in Chinese"
• "generating short videos from text or images at no cost for Chinese content creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Free Video Generation China — Generate Videos from Text Free

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 text prompt describing a mountain landscape scene and want to generate a 15-second video clip from my product description in Chinese — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter and more specific text prompts produce more accurate video results.

Matching Input to Actions

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

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

• X-Skill-Source: free-video-generation-china
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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.

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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 15-second video clip from my product description in Chinese" — 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 Chinese platforms like Douyin and Bilibili.

Common Workflows

Quick edit: Upload → "generate a 15-second video clip from my product description in Chinese" → 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.