Video Generation Ai

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

Security Scan

The skill's declared purpose (cloud video generation) matches most of its runtime instructions, but there are inconsistencies around local config access and where credentials/sessions are stored that you should review before installing.

Purpose & Capability

The skill is a cloud video generator and requests a single service credential (NEMO_TOKEN) and network access to a nemo-video API — this is proportionate to the stated purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier listed no required config paths; that discrepancy is unexplained.

Instruction Scope

Instructions direct the agent to obtain an anonymous token if NEMO_TOKEN is absent, create sessions, upload media, read SSE streams, and poll export endpoints — all expected for a cloud render pipeline. The skill also instructs to 'auto-detect' the X-Skill-Platform header from an install path (which could implicitly ask the agent to inspect the environment/install location). The instructions do not request unrelated system files, but they do imply storing tokens/session IDs locally without a clear, declared storage location.

Install Mechanism

No install spec or code files are present (instruction-only). Nothing will be downloaded or written by an installation step defined in the registry, which reduces install-time risk.

Credentials

Only one credential (NEMO_TOKEN) is declared, which fits the use-case. But the SKILL.md claims it may generate and persist an anonymous token and references a config path (~/.config/nemovideo/) in the frontmatter; the registry metadata does not declare that config path. Storing credentials or session IDs to disk would require explicit disclosure. Also the skill mandates sending Authorization: Bearer <NEMO_TOKEN> on every request and adding three custom attribution headers — these are operationally reasonable but mean the token will be routinely sent to the third-party domain.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It does, however, imply persistence by storing session_id and possibly an anonymous token for 7-day validity; where these values are stored is not clearly declared. No operations that modify other skills or system-wide settings are described.

What to consider before installing

This skill generally behaves like a cloud video generator: it will send uploaded media and prompts to https://mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (it can create an anonymous one if you don't supply one). Before installing, consider: 1) Where will the skill store the anonymous token/session ID on disk? Confirm whether it writes to ~/.config/nemovideo/ (the SKILL.md mentions that path but the registry metadata does not). 2) If you care about privacy, do not upload sensitive images/scripts — uploads go to a third party. 3) Prefer providing your own scoped NEMO_TOKEN (and rotate it) rather than allowing the skill to auto-create persistent tokens. 4) Ask the publisher for a homepage/privacy policy and clarify data retention and deletion of uploaded media and anonymous tokens. 5) If you need the agent not to act autonomously, control invocation policies in your agent rather than relying on the skill. If the maintainer cannot explain the config-path/token storage discrepancy and how/where credentials are stored, treat the mismatch as a red flag and avoid installing.

Getting Started

Send me your text prompts or images and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "generate a short text description of a product demo scene into a 1080p MP4"
• "generate a 30-second product explainer video from this script"
• "generating short videos from text prompts or images for marketers, content creators, social media managers"

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.

Video Generation AI — Generate Videos from Text or Images

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 product explainer video from this script — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

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

Matching Input to Actions

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

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

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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.

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

Common Workflows

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