Ai Video Creation

Get finished MP4 video ready to post, without touching a single slider. Upload your images or clips (MP4, MOV, JPG, PNG, up to 500MB), say something like "tu...

Security Scan

The skill's requests and runtime instructions align with a cloud video-rendering service: it needs a service token, uploads media, and calls the provider's API — nothing requested appears unrelated to the stated purpose.

Purpose & Capability

The skill name and description (AI video creation/export) align with the required Authorization token (NEMO_TOKEN) and the documented upload/render API calls. One minor mismatch: the metadata declares a config path (~/.config/nemovideo/) that the SKILL.md does not actually instruct the agent to read or write; this is likely benign but unnecessary.

Instruction Scope

SKILL.md instructs only to obtain/use a NEMO_TOKEN, create a session, upload media, and call render endpoints on mega-api-prod.nemovideo.ai. There are no instructions to read unrelated local files or other environment variables, nor to transmit data to unexpected endpoints.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is the lowest-risk install model and consistent with the skill's purpose.

Credentials

The only required credential is NEMO_TOKEN (declared as primary), which is appropriate for a remote video API. The skill also documents how to obtain an anonymous token automatically if none is present — reasonable. The metadata's configPaths entry suggests potential access to ~/.config/nemovideo/, but the runtime instructions do not reference reading that path; this is an inconsistency worth noting but not necessarily malicious.

Persistence & Privilege

The skill is not 'always' enabled and does not request elevated platform-wide privileges. It can be invoked autonomously (default), which is expected behavior for skills; there is no evidence it modifies other skills or system-wide settings.

Assessment

This skill will upload whatever media and text you provide to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (either one you set or an anonymous token it obtains for you). Before installing or using it: 1) Confirm you are comfortable uploading the media you provide (avoid sensitive personal or proprietary content). 2) If you prefer not to have the skill automatically obtain a token, set a token you control in NEMO_TOKEN or avoid using the skill. 3) Note the metadata references a local config path (~/.config/nemovideo/) though the instructions don't use it — if you see the agent reading or writing that directory, treat it as unexpected and investigate. 4) Verify the service domain and privacy policy if you need retention/usage guarantees. 5) If you do not want the skill to run autonomously, disable model invocation or adjust skill permissions in your agent settings.

Getting Started

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

Try saying:

• "create five product images and a script into a 1080p MP4"
• "turn these images and script into a 30-second promo video with music and transitions"
• "generating videos from images and text prompts for marketers and content creators"

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.

AI Video Creation — Create and Export Videos with AI

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

A quick example: upload five product images and a script, type "turn these images and script into a 30-second promo video with music and transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: using fewer than 10 images keeps generation time under a minute.

Matching Input to Actions

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

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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Common Workflows

Quick edit: Upload → "turn these images and script into a 30-second promo video with music and transitions" → 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 "turn these images and script into a 30-second promo video with music and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.