Best Video Generator

generate text prompts or clips into polished MP4 videos with this skill. Works with MP4, MOV, WebM, JPG files up to 500MB. marketers, content creators, small...

Security Scan

The skill's declared requirements and runtime instructions are consistent with a cloud video-generation integration that uses a single service token; nothing requested looks disproportionate to that stated purpose.

Purpose & Capability

Name/description (generate videos from text/media) align with the runtime instructions calling a remote 'nemovideo' API and the single required env var (NEMO_TOKEN). The declared config path (~/.config/nemovideo/) and the token are appropriate for a client that talks to a cloud rendering service.

Instruction Scope

Instructions focus on creating sessions, uploading media, streaming SSE, polling render status, and exporting videos — all within the stated purpose. Minor scope note: the skill asks the agent to detect the install platform by looking for install-path markers (e.g., ~/.clawhub/, ~/.cursor/skills/) to set an attribution header; this requires probing certain paths in the home tree and is not strictly necessary for core functionality.

Install Mechanism

No install spec and no code files (instruction-only). Lowest-risk distribution: nothing is downloaded or written to disk by an installer step in the skill itself.

Credentials

Only one environment credential is declared (NEMO_TOKEN) and it is directly relevant to authenticating with the external video service. The SKILL.md also documents an anonymous-token flow if NEMO_TOKEN is absent. No unrelated secrets or broad system credentials are requested.

Persistence & Privilege

always is false and the skill uses the normal model-invocation behavior. It does request reading a specific config path (~/.config/nemovideo/) and may probe for expected install paths to set an attribution header, but it does not request elevated or platform-wide persistent privileges.

Assessment

This skill is coherent for a cloud video generator, but note: any media or text you submit and the NEMO_TOKEN (or the anonymous token it fetches) will be sent to mega-api-prod.nemovideo.ai — only use it for content you are comfortable uploading. If you don't want a persistent token in your environment, omit NEMO_TOKEN and let the skill use the anonymous-token flow (ephemeral token with limited credits). Be aware the skill may probe certain home-directory paths to set an attribution header; if you are uncomfortable with that, do not install or invoke the skill. Because the skill's source and homepage are not provided, verify you trust the external API operator before supplying sensitive media or credentials.

Getting Started

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

Try saying:

• "generate my text prompts or clips"
• "export 1080p MP4"
• "generate a 60-second promo video from"

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.

Best Video Generator — Generate Videos from Text or Media

Send me your text prompts 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 a 200-word product description script, type "generate a 60-second promo video from this script with visuals and music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter scripts under 90 seconds produce the most coherent AI-generated results.

Matching Input to Actions

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

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

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

Common Workflows

Quick edit: Upload → "generate a 60-second promo video from this script with visuals and music" → 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 "generate a 60-second promo video from this script with visuals and music" — concrete instructions get better results.

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

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