Best Video Generation

Turn a short text prompt describing a sunset timelapse over a city into 1080p AI generated videos just by typing what you need. Whether it's generating video...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud video-generation integration: it only asks for a single service token (NEMO_TOKEN) and calls the nemovideo API endpoints described in the SKILL.md.

Purpose & Capability

The skill's name/description (generate videos from text) matches its declared requirement (NEMO_TOKEN) and all API endpoints target the nemovideo service. No unrelated credentials or external services are requested.

Instruction Scope

Instructions are focused on authenticating, creating sessions, streaming SSE, uploading user media, polling render jobs, and returning download URLs. They do instruct the agent to perform multipart file uploads using local paths (e.g., -F "files=@/path") and to save session_id/token state — which is expected for an upload/render flow, but you should be aware that uploads send user files and prompts to the remote API and that the agent is asked to persist session/token state.

Install Mechanism

This is an instruction-only skill with no install specification and no external downloads or packages — lowest-risk install footprint.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportional to the stated cloud-rendering purpose. The frontmatter also references a config path (~/.config/nemovideo/) for saving state; the registry metadata earlier listed no config paths — a minor metadata inconsistency worth confirming (where tokens/session state will be stored).

Persistence & Privilege

The skill does not request always:true and does not demand system-wide privileges. It expects to store session state/token (implied by 'Save session_id' and configPaths). Persisting a bearer token locally is normal here but increases the blast radius if the token is leaked or reused; be aware of where the agent will write such data.

Assessment

This skill appears to do what it says: it will send your text prompts and any uploaded media to a remote nemovideo API and requires a single bearer token (NEMO_TOKEN). Before installing or using it, consider: (1) Who controls the endpoint (https://mega-api-prod.nemovideo.ai) and whether you trust them with any media you upload or prompt text you provide. (2) Providing NEMO_TOKEN grants access to render and account actions — prefer using an account/token with minimal privileges or an anonymous token if available, and revoke it when no longer needed. (3) The skill may persist session_id/token to a config path (frontmatter mentions ~/.config/nemovideo/) — confirm where credentials are stored and secure that location. (4) If you will upload sensitive files, verify the service's privacy/retention policy first. (5) The metadata has a small inconsistency (registry said no config paths while the skill frontmatter lists one) — ask the publisher or inspect where the agent stores state before trusting persistent tokens. If you don't trust the remote service or don't want files sent off-host, do not provide a token or upload files.

Getting Started

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

Try saying:

• "generate a short text prompt describing a sunset timelapse over a city into a 1080p MP4"
• "generate a 30-second cinematic video of a futuristic cityscape at night"
• "generating videos from text prompts or images for marketers, content creators, social media managers"

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.

Best Video Generation — Generate Videos from Text Prompts

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

Here's a typical use: you send a a short text prompt describing a sunset timelapse over a city, ask for generate a 30-second cinematic video of a futuristic cityscape at night, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter, more specific prompts tend to produce more accurate and consistent results.

Matching Input to Actions

User prompts referencing best 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.

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.

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

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

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

Common Workflows

Quick edit: Upload → "generate a 30-second cinematic video of a futuristic cityscape at night" → 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 cinematic video of a futuristic cityscape at night" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, WebM, GIF for the smoothest experience.

Export as MP4 for widest compatibility across platforms and devices.