Easy Ai Video Generator

Cloud-based easy-ai-video-generator tool that handles generating polished videos from text or images without manual editing. Upload MP4, MOV, JPG, PNG files...

Security Scan

The skill's requests and runtime instructions match its stated purpose (cloud video generation) and it only needs a single service token, but there are minor inconsistencies (a declared config path and install-path probing) you should be aware of before use.

Purpose & Capability

Name/description (cloud video generation) align with the runtime instructions: creating sessions, uploading media, SSE chat, and exporting renders to an external nemovideo.ai backend. The only required credential is NEMO_TOKEN which is appropriate for a cloud API.

Instruction Scope

SKILL.md stays within the video-generation flow (token check/create, session creation, upload, SSE, export/poll). Two items to note: (1) it instructs checking for NEMO_TOKEN in the environment and using it if present (expected), and (2) it describes deriving X-Skill-Platform by inspecting install paths (~/.clawhub/, ~/.cursor/skills/), and the metadata declares a config path (~/.config/nemovideo/) — the instructions do not explicitly state what will be read from that config path but the presence of the path suggests the skill may look for saved tokens/config there. This is minor but worth being explicit about.

Install Mechanism

No install spec and no code files — instruction-only skill. Nothing is written to disk or downloaded by the skill itself according to the provided files.

Credentials

Only NEMO_TOKEN is required (declared as primary). That is proportionate to a cloud video-generation service. Caveat: because the skill will use any NEMO_TOKEN found in the environment (or potentially look in ~/.config/nemovideo/ per metadata), a pre-existing token in your environment would be used to charge or access your account — confirm that any NEMO_TOKEN present is intended for this service.

Persistence & Privilege

The skill is not force-enabled (always: false) and has no install actions or hooks that request persistent privileges or modify other skills/config. Autonomous invocation is allowed (default) but this is normal for skills and not an additional red flag here.

Assessment

This skill appears to do what it says: it calls nemovideo.ai endpoints to create sessions, upload media, and render videos. Before installing or invoking: 1) Check your environment for a NEMO_TOKEN — if you have one, the skill will use it and may charge or consume credits on that account; remove or rotate it if you don't want that. 2) Be aware the skill will call https://mega-api-prod.nemovideo.ai and may create anonymous tokens if none exist (these expire in 7 days). 3) The frontmatter mentions a config path (~/.config/nemovideo/) and the instructions derive a platform header by probing common install directories — if you want to avoid any filesystem checks, run the skill in a restricted/sandboxed environment or remove NEMO_TOKEN from your environment. 4) Avoid uploading sensitive or private video/audio assets unless you trust the service and its privacy terms.

Getting Started

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

Try saying:

• "generate my text or images"
• "export 1080p MP4"
• "create a 30-second product video 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.

Easy AI Video Generator — Generate Videos from Text or Images

Drop your text or images 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 script or three product photos, ask for create a 30-second product video from my photos and this script, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter scripts under 60 words generate faster and tend to produce tighter, more focused videos.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is easy-ai-video-generator, 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).

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

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.

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 → "create a 30-second product video from my photos and this script" → 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 "create a 30-second product video from my photos and this script" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and websites.