Best Video Generator Ai

generate text prompts or clips into AI-generated videos with this skill. Works with MP4, MOV, PNG, JPG files up to 500MB. marketers, content creators, entrep...

Security Scan

The skill's behavior mostly matches a cloud video-generation service, but there are inconsistencies in declared requirements (a config path requested in the SKILL.md frontmatter but not in registry metadata) and the skill will upload user media to an external API — you should confirm data handling and the service before installing or supplying credentials.

Purpose & Capability

The name/description match the runtime instructions: the SKILL.md describes calling a NemoVideo backend to create videos and requires a NEMO_TOKEN. However the SKILL.md frontmatter includes a required configPaths entry (~/.config/nemovideo/) while the registry metadata shown to you lists no required config paths — this discrepancy is unexplained and worth verifying.

Instruction Scope

Instructions are concrete and focused on the external API: create a session, run SSE for generation, upload files, poll render status, and download output. This is consistent with a video-generation skill. Important operational notes: the skill will upload user-provided media (potentially up to 500MB) to an external service (mega-api-prod.nemovideo.ai), will read this skill's own frontmatter at runtime, and directs the agent to detect install paths (reading ~ paths) for an attribution header — these filesystem reads and large uploads are expected for the stated purpose but are privacy-sensitive and should be understood by the user.

Install Mechanism

This is instruction-only with no install spec or binaries. That is the lowest-risk install mechanism — nothing is written to disk by an installer step in the registry metadata.

Credentials

The primaryEnv is NEMO_TOKEN, which is appropriate for an API-backed video service. But the SKILL.md frontmatter claims it requires access to ~/.config/nemovideo/, which could contain stored tokens or config; the published registry metadata did not list that config path. This mismatch could lead to unexpected file access. Also, if you do not provide NEMO_TOKEN the skill will request an anonymous token from the external API and use it — this is reasonable but you should confirm what permissions and retention that token grants.

Persistence & Privilege

always is false and the skill does not request persistent/always-on privileges or modification of other skills. There is no install-time persistence requested in the metadata.

What to consider before installing

What to check before installing or using this skill: - Confirm the service domain (mega-api-prod.nemovideo.ai) is legitimate and review its privacy/terms: using this skill will upload your video/image/audio files to that external service. - Do not supply a high-privilege or long-lived NEMO_TOKEN unless you trust the service. Prefer using the anonymous token flow if you want limited, short-lived access. - Ask the skill author/provider: why does the frontmatter request ~/.config/nemovideo/ while the registry shows no required config paths? Understand exactly what files (if any) the skill will read from your home directory. - If you must upload sensitive media, confirm retention, access controls, and deletion policies on the backend. - If you are uncomfortable with file uploads or possible filesystem reads, do not install or invoke the skill, or run it in an environment with limited access (e.g., without placing credentials or sensitive files on the host). If you want higher confidence, request the publisher/source URL, a privacy policy, and clarification about the frontmatter configPaths mismatch; with those answers the classification could be upgraded to benign.

Getting Started

Send me your text prompts or clips and I'll handle the AI video generation. Or just describe what you're after.

Try saying:

• "generate a short text description of a product launch scene into a 1080p MP4"
• "generate a 30-second promotional video from my product description"
• "generating videos from text prompts or images without filming for marketers, content creators, entrepreneurs"

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.

Best Video Generator AI — Generate Videos from Text or Images

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

Say you have a short text description of a product launch scene and want to generate a 30-second promotional video from my product description — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter, specific prompts produce more accurate and consistent video output.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: best-video-generator-ai
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second promotional video from my product description" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "generate a 30-second promotional video from my product description" → 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.