Ai Video Generator Free Heygen

Skip the learning curve of professional editing software. Describe what you want — create a talking avatar video from my script using a free HeyGen-style AI...

Security Scan

The skill's behavior mostly matches an AI video generator, but there are inconsistencies and a few surprising behaviors (automatic anonymous token creation, implied local config/Install-path probing, and mismatched metadata) that warrant caution before installing.

Purpose & Capability

Name/description describe an online AI avatar video generator and the skill only needs a single service token (NEMO_TOKEN) — that aligns. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata shown earlier reported no required config paths; this mismatch is unexplained and worth verifying.

Instruction Scope

Instructions direct the agent to call multiple external endpoints on mega-api-prod.nemovideo.ai, upload local files (up to 200MB) and manage session tokens. They also instruct deriving an attribution header value from local install paths (e.g. checking ~/.clawhub/ or ~/.cursor/skills/), which implies the agent will probe the filesystem. The skill will automatically request an anonymous token if NEMO_TOKEN is not present. These are reasonable for a cloud render service but broaden what the agent will access (local paths, filesystem) and do (network token creation) beyond just 'take a script and render a video.'

Install Mechanism

No install spec or code is present; the skill is instruction-only and does not write files or download archives. This is lower-risk than an installer that fetches binaries.

Credentials

The skill only declares one required env var (NEMO_TOKEN), which matches the service. But the SKILL.md will create an anonymous token if the env var is missing and also references a local config path in its metadata; confirm whether the skill expects to read ~/.config/nemovideo/ or persist tokens there. That combination slightly increases the scope of sensitive data access.

Persistence & Privilege

The skill is not force-installed (always: false) and uses normal autonomous invocation. It does not request elevated platform-wide privileges in the provided instructions.

What to consider before installing

Before installing: 1) Understand that this skill will send any uploaded files and prompts to https://mega-api-prod.nemovideo.ai — do not upload sensitive material you don't want transmitted. 2) The skill will use NEMO_TOKEN if present, or automatically request an anonymous token from the service; if you care about control or auditability, provide your own token rather than allowing anonymous issuance. 3) Confirm the domain and service are legitimate for your use; the skill probes local install paths (~/.clawhub/, ~/.cursor/skills/) and may read ~/.config/nemovideo/ per its frontmatter — if you have secrets or tokens stored in those locations, be cautious. 4) There's an inconsistency between the registry metadata (no config paths) and the SKILL.md frontmatter (declares a config path); ask the publisher to clarify where tokens/config are stored and whether anything is persisted locally. Proceed only if you trust the remote service and are comfortable with large-file uploads and token usage.

Getting Started

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

Try saying:

• "generate a 150-word product description script into a 1080p MP4"
• "create a talking avatar video from my script using a free HeyGen-style AI presenter"
• "generating avatar spokesperson videos from text scripts for free for marketers"

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.

AI Video Generator Free HeyGen — Generate AI Avatar Presenter Videos

Send me your text or script and describe the result you want. The AI avatar video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 150-word product description script, type "create a talking avatar video from my script using a free HeyGen-style AI presenter", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter scripts under 60 seconds render significantly faster and use fewer credits.

Matching Input to Actions

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

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 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

Common Workflows

Quick edit: Upload → "create a talking avatar video from my script using a free HeyGen-style AI presenter" → 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 talking avatar video from my script using a free HeyGen-style AI presenter" — concrete instructions get better results.

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

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