How To Create Ai Video

Turn five product photos and a voiceover MP3 into 1080p AI-generated videos just by typing what you need. Whether it's generating videos from images and audi...

Security Scan

The skill's requirements and runtime instructions are consistent with its stated purpose (remote AI video generation) and do not ask for unrelated secrets or installs, but you should verify and trust the external API domain before sending sensitive content or long-lived credentials.

Purpose & Capability

The skill declares a single credential (NEMO_TOKEN) and its instructions use that token to call an external video-rendering API (mega-api-prod.nemovideo.ai). Requiring an API token and a config path under ~/.config/nemovideo/ is coherent with a cloud video-rendering service.

Instruction Scope

SKILL.md instructs only API calls (session creation, SSE chat, upload, export, polling) and to read the skill's own YAML frontmatter for attribution. It does not instruct the agent to read arbitrary system files, user credentials, or unrelated environment variables. It does suggest detecting install path for attribution headers (limited scope).

Install Mechanism

No install spec or external downloads — instruction-only skill. This is the lowest-risk install model and matches the described cloud-only rendering approach.

Credentials

Only NEMO_TOKEN is required (primaryEnv). The fallback anonymous-token flow is described for when NEMO_TOKEN is absent. There are no unrelated credential requests (no AWS/GCP keys, no SSH keys). The skill mentions a config path (~/.config/nemovideo/) which is reasonable for storing service-specific config.

Persistence & Privilege

The skill is not always-on and does not request elevated or system-wide persistence. It does not instruct modification of other skills or global agent settings.

Assessment

This skill appears coherent: it sends user-provided images/audio to a remote video-rendering API and needs a NEMO_TOKEN to authenticate. Before installing or using it, confirm you trust the service domain (mega-api-prod.nemovideo.ai) and review its privacy/retention policy — uploaded media will be transmitted to that backend. Prefer using a short-lived or limited-scope token if possible; avoid placing unrelated secrets (AWS keys, database passwords, etc.) into NEMO_TOKEN. If you don't provide NEMO_TOKEN, the skill will obtain an anonymous starter token automatically (100 free credits for 7 days). If you need higher assurance, ask the skill author for a privacy/data-retention statement or run uploads with non-sensitive test media first.

Getting Started

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

Try saying:

• "create five product photos and a voiceover MP3 into a 1080p MP4"
• "turn these photos and audio into a 30-second promo video with transitions"
• "generating videos from images and audio without manual editing for marketers and content creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

How To Create AI Video — Generate Videos from Your Assets

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 photos and a voiceover MP3, type "turn these photos and audio into a 30-second promo video with 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 how to create ai video, 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: how-to-create-ai-video
• 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 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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these photos and audio into a 30-second promo video with 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 across social platforms and devices.

Common Workflows

Quick edit: Upload → "turn these photos and audio into a 30-second promo video with 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.