Explicit Ai Video Generator Free

Get AI generated videos ready to post, without touching a single slider. Upload your text prompts (MP4, MOV, WebM, GIF, up to 500MB), say something like "gen...

Security Scan

The skill's requested access and runtime behavior are consistent with a cloud video-generation utility: it asks for one service token, uploads user media to a remote API, and has no install step or unrelated credential requests.

Purpose & Capability

Name/description, required env var (NEMO_TOKEN), and declared API endpoints all align with a cloud video-generation service. No unrelated credentials or binaries are requested.

Instruction Scope

SKILL.md confines actions to creating sessions, uploading user media (multipart or via URL), sending SSE messages, polling render status, and returning downloads — all expected for this purpose. Minor inconsistency: metadata lists a config path (~/.config/nemovideo/) but the runtime instructions never explicitly say to read that path (they only check NEMO_TOKEN in environment or obtain an anonymous token via the public endpoint). The skill will send user uploads and any URLs the user provides to an external API (mega-api-prod.nemovideo.ai), so users should not upload sensitive local files or private URLs.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing will be written to disk by an installer. This is the lowest-risk install profile.

Credentials

Only NEMO_TOKEN is required (declared as primary credential), which is proportional for a cloud API client. The presence of a declared config path in metadata could indicate the skill may want to access local config, but the instructions do not require reading other system credentials. The skill can mint an anonymous token if none is present (100 free credits, 7-day expiry).

Persistence & Privilege

always:false and user-invocable:true. The skill does not request permanent presence or platform-level privileges; it does not modify other skills or system-wide settings.

Assessment

This skill appears to do what it says: it sends your prompts and uploaded media to mega-api-prod.nemovideo.ai using a NEMO_TOKEN (or an anonymously obtained short-lived token) and returns a rendered video URL. Before installing/using it, consider: 1) The service will receive any files or URLs you upload — do not upload private or sensitive files. 2) If you provide your own NEMO_TOKEN, it grants API access to that account—treat it like a password. 3) The metadata mentions a local config path (~/.config/nemovideo/) even though instructions don't require reading it; verify whether the agent runtime will expose that path if you have existing nemo config. 4) The endpoint hostname is not a widely known vendor in this package; check the service's privacy/terms if you plan to upload user data or explicit content. If you need stronger assurance, ask the skill author for a homepage/privacy policy and for confirmation whether the skill will read any local config files beyond NEMO_TOKEN.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "generate a 30-second video of a"

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.

Explicit AI Video Generator Free — Generate Videos From Text Prompts

This tool takes your text prompts 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 scene or story idea and want to generate a 30-second video of a sunset beach scene with cinematic camera movement — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter, more specific prompts tend to produce more accurate and higher quality results.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	explicit-ai-video-generator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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 video of a sunset beach scene with cinematic camera movement" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "generate a 30-second video of a sunset beach scene with cinematic camera movement" → 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.