Video Generation Online

Turn a short text description of a product demo scene into 1080p ready-to-share videos just by typing what you need. Whether it's generating videos from text...

Security Scan

The skill mostly behaves like a text→video client (network calls, uploads, session tokens) but contains small metadata inconsistencies and asks the agent to transmit user content and create anonymous tokens against an external API — review before installing.

Purpose & Capability

Name/description (text→video) match the runtime instructions (upload, SSE, render, export). Requiring NEMO_TOKEN is expected. However the skill frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported none — this mismatch is inconsistent. The skill also provides an anonymous-token fallback if NEMO_TOKEN is absent, which is plausible but makes the declared 'required env var' semantics a bit ambiguous.

Instruction Scope

SKILL.md explicitly instructs the agent to: check environment for NEMO_TOKEN, optionally POST to an external auth endpoint to obtain an anonymous token, create sessions, upload files (multipart or URL), and stream SSE responses. All of this is coherent with video generation. The important runtime behavior is that user prompts/files are sent to https://mega-api-prod.nemovideo.ai — this is expected but has privacy implications. The instructions are somewhat vague about the exact attribution headers (mentions 'three attribution headers above') and about how long tokens/sessions are persisted.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. Nothing written to disk by an install step in the package itself.

Credentials

Only one declared env var (NEMO_TOKEN) — appropriate for a cloud API client. However the SKILL.md will obtain an anonymous token by calling the service if NEMO_TOKEN is missing, so the practical need for providing your own token is optional. The frontmatter's mention of a config path (~/.config/nemovideo/) (missing from registry metadata) suggests the skill may try to read user config for attribution — this should be clarified before trusting it with sensitive config files.

Persistence & Privilege

No 'always: true'. The skill instructs keeping session_id in memory for operations but does not request system-wide persistent privileges. Autonomous invocation is allowed by default but not combined here with elevated privileges.

What to consider before installing

This skill will upload your prompts and any files you provide to an external service (mega-api-prod.nemovideo.ai) and will request or mint short-lived tokens to operate. That behavior is consistent with a cloud video-generation tool, but you should: (1) avoid sending sensitive content (private data, secrets, PII) to the service; (2) prefer using an anonymous token or a dedicated limited-scope token rather than a long-lived production token; (3) ask the publisher for the official homepage, privacy policy, and who runs the mega-api-prod.nemovideo.ai domain before installing; (4) ask the author to clarify the config path behavior (frontmatter lists ~/.config/nemovideo/ but registry metadata did not) and to enumerate the exact headers and data the skill will send. Because this is instruction-only with no packaged code, there's nothing else to audit beyond SKILL.md — treat network/transmit behavior and metadata inconsistencies as the main risk factors.

Getting Started

Ready when you are. Drop your text prompts or images here or describe what you want to make.

Try saying:

• "generate a short text description of a product demo scene into a 1080p MP4"
• "generate a 30-second explainer video from this script"
• "generating videos from text prompts or images without filming anything for marketers, content creators, small business owners"

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.

Video Generation Online — Create Videos from Text Prompts

This tool takes your text prompts or images and runs AI video creation 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 demo scene and want to generate a 30-second explainer video from this script — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter, specific prompts produce more accurate and consistent results.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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

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)

Common Workflows

Quick edit: Upload → "generate a 30-second explainer video from this script" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second explainer video from this script" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and websites.