Ai Video Generator Free Invideo

v1.0.0

Turn a 150-word product description script into 1080p ready-to-share videos just by typing what you need. Whether it's generating videos from text scripts wi...

0· 72·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mhogan2013-9/ai-video-generator-free-invideo.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Ai Video Generator Free Invideo" (mhogan2013-9/ai-video-generator-free-invideo) from ClawHub.
Skill page: https://clawhub.ai/mhogan2013-9/ai-video-generator-free-invideo
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install ai-video-generator-free-invideo

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-video-generator-free-invideo
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (AI video generation) match the declared primary env var (NEMO_TOKEN) and the SKILL.md which calls a nemovideo.ai API. Requiring a service token is expected for a cloud rendering pipeline.
Instruction Scope
Runtime instructions describe creating/using a NEMO_TOKEN, opening a session, uploading files (multipart or URL), talking to SSE endpoints, and saving session_id. These actions align with the stated purpose, but the skill expects the agent to upload user files and persist session state (session_id) — users should expect their text and any uploaded media will be sent to mega-api-prod.nemovideo.ai. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) which is not reflected in the registry metadata; this discrepancy is minor but worth noting.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is downloaded or written to disk by an installer, which minimizes install-time risk.
Credentials
Only one credential (NEMO_TOKEN) is required and it is the natural credential for the described API. The token can be provided via environment or obtained anonymously via the documented endpoint. No unrelated secrets or multiple credentials are requested.
Persistence & Privilege
always is false; the skill can be invoked by the agent but does not request permanent platform-wide privileges. It does instruct saving session_id and using/storing a token for subsequent calls, which is normal for an API-backed tool and limited in scope to this service.
Assessment
This skill will send your prompt text and any media you upload to mega-api-prod.nemovideo.ai and will create or use a NEMO_TOKEN (either from your env or by requesting an anonymous token). If you have sensitive content, avoid uploading it. Be aware the skill will persist session identifiers so you can continue a job; if you prefer not to persist credentials, unset NEMO_TOKEN or revoke the anonymous token after use. Note the SKILL.md references a local config path (~/.config/nemovideo/) that isn't declared in the registry metadata — this likely just indicates where the service client would store state, but you may want to confirm whether any local files are read or written before installing.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97c297125atk94ypbfkreb14s84yax1
72downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

Ready when you are. Drop your text prompts here or describe what you want to make.

Try saying:

  • "generate a 150-word product description script into a 1080p MP4"
  • "create a 60-second promotional video from this script with background music and transitions"
  • "generating videos from text scripts without manual editing for marketers"

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 Video Generator Free InVideo — Generate Videos from Text Scripts

This tool takes your text prompts and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 150-word product description script and want to create a 60-second promotional video from this script with background music and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 100 words generate faster and tend to produce tighter, more focused videos.

Matching Input to Actions

User prompts referencing ai video generator free invideo, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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:

HeaderValue
X-Skill-Sourceai-video-generator-free-invideo
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-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.

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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 saysYou 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 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

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Common Workflows

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

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

Export as MP4 for widest compatibility across social platforms.

Comments

Loading comments...