Video Explainer Ai

Turn a 300-word product explanation script into 1080p narrated explainer videos just by typing what you need. Whether it's creating explainer videos from scr...

Security Scan

The skill largely matches its stated purpose (driving a nemovideo API) but has small inconsistencies and asks the agent to inspect local install paths for attribution — behaviors that are unnecessary for video rendering and worth questioning before install.

Purpose & Capability

Name/description (produce explainer videos) aligns with the runtime instructions and endpoints (nemovideo API). The single required environment variable NEMO_TOKEN is appropriate for an external rendering service. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch is an inconsistency that should be clarified with the publisher.

Instruction Scope

Instructions require contacting external endpoints (expected) and storing a session_id (expected). They also instruct the agent to read the skill's YAML frontmatter and detect the agent install path to populate an X-Skill-Platform header (check paths like ~/.clawhub/ and ~/.cursor/skills/). Detecting install paths or reading filesystem locations for attribution is outside the strict needs of video rendering and expands the agent's scope to inspect local filesystem layout — this is unnecessary for the stated task and should be justified or removed.

Install Mechanism

Instruction-only skill with no install spec and no code files. Low install risk because nothing is downloaded or written by an installer.

Credentials

Only NEMO_TOKEN is required, which matches the documented Bearer Authorization usage. The skill also documents an anonymous-token flow (POST to /api/auth/anonymous-token) when NEMO_TOKEN is absent — reasonable for a public service. No unrelated secrets or multiple credentials are requested. The earlier inconsistency about configPaths (frontmatter vs registry) weakly affects proportionality because reading config files could expose additional data if implemented.

Persistence & Privilege

always is false and the skill does not request system-wide privileges. It asks to save a session_id for the user session (normal). It does not request to modify other skills or force permanent presence.

What to consider before installing

This skill appears to be an instruction-only connector to a third‑party video rendering API (mega-api-prod.nemovideo.ai) and mostly asks for the expected API token (NEMO_TOKEN). Before installing, confirm you trust that external service — videos and any uploaded media will be sent to it. Ask the publisher to explain the configPath mismatch (SKILL.md lists ~/.config/nemovideo/ while registry metadata did not). Also ask why the skill needs to detect install paths (it reads the agent's install location to set X-Skill-Platform); if you prefer not to grant any filesystem probing, request that this attribution be removed or limited to safe metadata passed in explicitly. Finally, avoid sending sensitive or private content until you verify the provider's privacy policy and token handling; if you use the anonymous-token flow, remember those tokens have limited credits and expiry and can still expose your uploads to the service.

Getting Started

Got topic or script to work with? Send it over and tell me what you need — I'll take care of the AI explainer video creation.

Try saying:

• "generate a 300-word product explanation script into a 1080p MP4"
• "turn this script into an explainer video with visuals and voiceover"
• "creating explainer videos from scripts or topics using AI for marketers, educators, startup founders"

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.

Video Explainer AI — Generate Explainer Videos from Scripts

Drop your topic 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 300-word product explanation script, ask for turn this script into an explainer video with visuals 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 150 words produce tighter, more engaging explainer videos.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

• X-Skill-Source: video-explainer-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.

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

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.

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

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this script into an explainer video with visuals 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 presentations, websites, and social platforms.

Common Workflows

Quick edit: Upload → "turn this script into an explainer video with visuals 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.