Open Ai Video Generation

marketers generate text prompts into AI generated videos using this skill. Accepts MP4, MOV, WebM, GIF up to 500MB, renders on cloud GPUs at 1080p, and retur...

Security Scan

The skill's requests and runtime instructions line up with its stated purpose of cloud-based AI video generation; nothing requested is disproportionate, though users should be aware their media and anonymous tokens are uploaded to a third‑party API.

Purpose & Capability

Name/description (generate videos from text) matches the runtime instructions: authenticate to nemo-video API, create sessions, upload media, stream SSE edits, and request exports. The single required credential (NEMO_TOKEN) is appropriate for a hosted rendering API.

Instruction Scope

Instructions are narrowly scoped to API calls for session creation, SSE chat, uploads, state, credits, and export. They include logic to mint an anonymous token if NEMO_TOKEN is absent and to read the skill's own frontmatter and detect install path for attribution headers. The skill will upload user media (up to 500MB) and poll remote endpoints — users should expect their media and job metadata to be sent to mega-api-prod.nemovideo.ai.

Install Mechanism

No install steps or external downloads; instruction-only skill (no code files) so nothing is written to disk by an installer.

Credentials

Only NEMO_TOKEN is declared as required and used. The skill also describes obtaining an anonymous token from the vendor if none is present; no unrelated secrets or multiple credentials are requested.

Persistence & Privilege

Skill is not always-enabled and uses normal autonomous invocation. The SKILL.md suggests keeping session_id and reusing tokens (tokens expire in 7 days) but does not instruct writing to system-wide configs; users should confirm whether the agent will persist the anonymous token on disk or only in-memory.

Assessment

This skill appears coherent for its stated job, but before installing you should be aware: (1) using it will upload your media and job metadata to mega-api-prod.nemovideo.ai — do not upload sensitive or confidential footage unless you trust that service and its privacy/retention policy; (2) if you don't supply NEMO_TOKEN the skill will request an anonymous token from the vendor (100 free credits, 7‑day expiry) — check how/where that token is stored by your agent; (3) the SKILL.md mentions reading the skill's own frontmatter and detecting install paths for attribution headers (this may require limited filesystem access to known paths); and (4) there is a minor metadata discrepancy: the registry summary listed no config paths while the SKILL.md frontmatter lists ~/.config/nemovideo/ — confirm whether the agent will access that path. If you accept those privacy/network implications and trust the remote service, the skill is internally consistent.

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 scene into a 1080p MP4"
• "generate a 30-second video of a sunset over a city skyline with cinematic camera movement"
• "generating videos from text descriptions using AI for marketers"

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.

Open AI 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 scene, ask for generate a 30-second video of a sunset over a city skyline with cinematic camera movement, and about 1-3 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 open ai 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 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: open-ai-video-generation
• 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.

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 video of a sunset over a city skyline with cinematic camera movement" → 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 video of a sunset over a city skyline with cinematic camera movement" — 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.