Create A Video With Ai

Cloud-based create-a-video-with-ai tool that handles generating videos from images or clips without manual editing. Upload MP4, MOV, JPG, PNG files (up to 50...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud video-generation tool: it only asks for a single service token (NEMO_TOKEN) and describes using that token to call the documented API endpoints; nothing else looks disproportionate or unrelated to the stated purpose.

Purpose & Capability

Name/description, required env var (NEMO_TOKEN), declared config path (~/.config/nemovideo/), and the API endpoints in SKILL.md all align with a cloud video-generation service.

Instruction Scope

Instructions are focused on authenticating, creating a session, uploading assets, streaming SSE, and exporting results. Minor implementation notes ask the agent to detect an install path to set X-Skill-Platform and to 'save session_id' (ambiguous whether ephemeral or persisted). These are not inherently malicious but are implementation details the integrator should confirm (e.g., how/where session_id is stored).

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is downloaded or written by the skill itself during install.

Credentials

Only one environment variable (NEMO_TOKEN) is required and it is the expected credential for a cloud API. No unrelated credentials or secrets are requested.

Persistence & Privilege

Skill is not always-on and does not request elevated platform privileges. Autonomous invocation is allowed (default) but not combined with broad credentials or other red flags.

Assessment

This skill appears internally consistent for a cloud video generation service. Before installing, consider: (1) you will be uploading media to a remote service (mega-api-prod.nemovideo.ai) — do not send sensitive or private footage unless you trust the provider; (2) the source/homepage are missing and the registry owner is unknown — verify the service independently if possible; (3) the skill can create an anonymous token for you if NEMO_TOKEN isn't provided — that token grants access for 7 days to the service, so treat it like a credential; (4) ask or check where the agent will store session_id and tokens (ephemeral memory vs persistent config) if you need them removed later. If you cannot verify the remote service or its privacy/retention policies, avoid uploading sensitive data.

Getting Started

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

Try saying:

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

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.

Create a Video with AI — Generate Videos from Your Assets

This tool takes your images or clips and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have five product photos and a voiceover file and want to turn these photos and audio into a 30-second promo video with transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using fewer than 10 clips keeps generation time under a minute.

Matching Input to Actions

User prompts referencing create a video with 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.

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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is create-a-video-with-ai, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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

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

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.

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)

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