Free Explainer Video

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

Security Scan

The skill’s requirements and runtime instructions are consistent with its stated purpose: it connects to a Nemo cloud API using a NEMO_TOKEN, uploads user-provided media/scripts, creates render jobs, polls for completion, and returns download URLs.

Purpose & Capability

Name and description describe a cloud-based explainer-video service; the only required credential is NEMO_TOKEN and the described API endpoints and flows match that purpose. No unrelated credentials or binaries are requested.

Instruction Scope

Runtime instructions stay within the video-creation workflow (token check/anonymous-token fetch, session creation, SSE for edits, upload, export and polling). They require reading user-supplied files for upload. Minor mismatch: frontmatter lists a config path (~/.config/nemovideo/) but the SKILL.md does not explicitly describe reading or writing that config; the skill also auto-obtains an anonymous token if NEMO_TOKEN is absent.

Install Mechanism

Instruction-only skill with no install spec or code to download; lowest-risk installation surface.

Credentials

Only NEMO_TOKEN is declared as required and used as the Bearer credential for API calls, which is proportional. No unrelated secrets or many environment variables are requested.

Persistence & Privilege

always is false and the skill does not request elevated or persistent system privileges. There are no instructions to modify other skills or global agent settings.

Assessment

This skill appears to do what it says, but it uploads your scripts and media to a third-party cloud service (mega-api-prod.nemovideo.ai). Before installing/using: 1) Do not upload confidential or sensitive data unless you trust the service and have read its privacy/terms. 2) If you already have a Nemo account, prefer providing your own NEMO_TOKEN; otherwise the skill will request an anonymous token from the vendor. 3) Verify where downloaded files are served from before opening them. 4) Check whether the agent persists the anonymous token (e.g., in ~/.config/nemovideo/) and remove/revoke it if you stop using the skill. 5) If you need higher assurance, ask the publisher for a privacy/data-retention statement or a vetted service endpoint.

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"

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.

Free Explainer Video — 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 150-word product description, ask for create a 60-second explainer video from this script with animations and voiceover, 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 100 words produce tighter, more engaging explainer videos.

Matching Input to Actions

User prompts referencing free explainer video, 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	free-explainer-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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.

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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 "create a 60-second explainer video from this script with animations and voiceover" — 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 websites and presentations.

Common Workflows

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