Video Generative Ai

Get AI generated videos ready to post, without touching a single slider. Upload your text or images (MP4, MOV, PNG, JPG, up to 200MB), say something like "ge...

Security Scan

The skill's declared purpose (remote AI video generation) matches its instructions and requested credential (NEMO_TOKEN); nothing in the SKILL.md demands unrelated system access, but there are minor metadata inconsistencies and normal privacy/network concerns to consider before use.

Purpose & Capability

The name and description (AI video generation) align with the required credential (NEMO_TOKEN) and the SKILL.md which describes a cloud-render pipeline. Minor inconsistency: registry metadata earlier showed no required config paths, but the SKILL.md frontmatter metadata lists a config path (~/.config/nemovideo/). This mismatch should be clarified but doesn't imply malicious intent.

Instruction Scope

The instructions stay within the scope of a cloud video-generation client: check/use NEMO_TOKEN, obtain anonymous token if missing, create a session, upload media, stream SSE events, poll for export status, and download results. The skill asks to add attribution headers and to map GUI commands to API calls. It does not instruct reading unrelated system files or other environment secrets. One small note: it mentions auto-detecting X-Skill-Platform from the install path which may require access to the agent's environment/paths—this is plausible for attribution but should be explicit.

Install Mechanism

Instruction-only skill with no install spec and no code files—no files are written to disk by the skill itself. This is the lowest-risk install model.

Credentials

Only a single credential is requested (NEMO_TOKEN) and it is clearly the API bearer token needed to call the remote service. The SKILL.md also documents a safe fallback (anonymous-token endpoint) to obtain a short-lived token. No other unrelated credentials or secrets are requested.

Persistence & Privilege

always:false and the skill expects to hold a session_id for operations—this is appropriate for a remote render client. The skill does reference a config path in its frontmatter (possible local config usage), but it does not request system-wide privileges or modification of other skills' settings.

Assessment

This skill appears to do what it says: it talks to a remote nemovideo.ai API to generate videos and only needs a NEMO_TOKEN. Before installing: (1) Confirm you trust https://mega-api-prod.nemovideo.ai and review its privacy/terms—your uploaded media and prompts are sent to that remote service. (2) Clarify the metadata mismatch about ~/.config/nemovideo/ (the skill frontmatter references it even though the registry summary did not). (3) Use a limited-scope or ephemeral token (or rely on the anonymous-token flow) rather than a highly privileged account token. (4) Avoid uploading sensitive or private content to this service. (5) If you need stronger assurance, ask the publisher for a homepage/privacy policy or test with non-sensitive media and monitor network activity. If any of these checks fail or you can't verify the service, treat the skill as untrusted and do not provide long-lived credentials.

Getting Started

Share your text or images and I'll get started on AI video generation. Or just tell me what you're thinking.

Try saying:

• "generate my text or images"
• "export 1080p MP4"
• "generate a 30-second video clip from"

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 Generative AI — Generate Videos from Text Prompts

Send me your text or images and describe the result you want. The AI video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a short text prompt describing a sunset over mountains, type "generate a 30-second video clip from this description: a timelapse of city traffic at night", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.

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

Matching Input to Actions

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

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

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

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.

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.

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.

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

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 clip from this description: a timelapse of city traffic at night" → 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 clip from this description: a timelapse of city traffic at night" — 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.