Ai Explainer Video Free

Get animated explainer videos ready to post, without touching a single slider. Upload your text or script (TXT, DOCX, PDF, MP4, up to 200MB), say something l...

Security Scan

The skill's requests and instructions are consistent with a cloud video-rendering integration: it needs a single service token, calls a Nemovideo API, and uploads user media for rendering — nothing requested appears unrelated to its stated purpose.

Purpose & Capability

Name/description match the runtime instructions: the SKILL.md describes creating explainer videos via the Nemovideo API and the only required credential is NEMO_TOKEN. The declared config path (~/.config/nemovideo/) and primaryEnv (NEMO_TOKEN) are consistent with a client that may keep local state or credentials.

Instruction Scope

Instructions direct the agent to obtain/use an API token, create sessions, send SSE and multipart uploads, poll render status, and return download URLs — all expected for a render service. Two points to note: (1) the skill will upload user files to an external domain (https://mega-api-prod.nemovideo.ai), so any uploaded content is sent off-agent; (2) the skill asks the agent to read its own frontmatter and detect install paths to set attribution headers, which requires limited filesystem inspection (its own SKILL.md and checking typical install paths). There are no instructions to read unrelated user files or environment variables.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is downloaded or written to disk by an installer in the skill bundle, which is the lowest-risk installation model.

Credentials

Only one secret is requested (NEMO_TOKEN), which is proportionate for a third-party API. The SKILL.md also supports generating an anonymous token if none is provided. No other unrelated credentials or secrets are requested.

Persistence & Privilege

always:false and no install-time modifications or requests to change other skills' configs. The skill asks to save a session_id (expected for session management) but does not request persistent elevated privileges or system-wide changes.

Assessment

This skill appears to do what it says: it uses a single Nemovideo token and uploads your scripts/media to a Nemovideo API to produce rendered videos. Before installing, consider: (1) NEMO_TOKEN is a secret — don’t reuse or store highly sensitive credentials there; (2) any files you upload will be transmitted to https://mega-api-prod.nemovideo.ai — avoid uploading confidential material unless you trust the service and its terms; (3) the skill may generate and store an anonymous token if you don’t provide one (7‑day expiry); (4) the skill reads its own metadata and checks common install paths to populate attribution headers — it does not ask to read arbitrary files. If you need stronger guarantees about data handling or retention, verify Nemovideo’s privacy/security policies before use.

Getting Started

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

Try saying:

• "create my text or script"
• "export 1080p MP4"
• "create a 60-second explainer 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.

AI Explainer Video Free — Create Explainer Videos from Text

Drop your text or script in the chat and tell me what you need. I'll handle the AI explainer video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 200-word product description or topic outline, ask for create a 60-second explainer video from this script with voiceover and animations, 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 150 words produce the most focused and polished explainer videos.

Matching Input to Actions

User prompts referencing ai explainer video 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

• X-Skill-Source: ai-explainer-video-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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.

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)

Common Workflows

Quick edit: Upload → "create a 60-second explainer video from this script with voiceover and animations" → 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 60-second explainer video from this script with voiceover and animations" — concrete instructions get better results.

Max file size is 200MB. Stick to TXT, DOCX, PDF, MP4 for the smoothest experience.

Export as MP4 for widest compatibility across YouTube, websites, and presentations.