Free Video Generator Like Invideo

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

Security Scan

The skill's required credential (NEMO_TOKEN), endpoints, and runtime instructions are coherent with a remote AI video-generation service; minor metadata and telemetry/header-detection details deserve attention but do not indicate misdirection.

Purpose & Capability

The skill claims to create videos via a remote NemoVideo backend and requires a NEMO_TOKEN — that aligns with the described functionality. Minor inconsistency: the registry metadata listed no config paths, but the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/), which is not explained by the registry manifest.

Instruction Scope

Runtime instructions are focused on authenticating (use NEMO_TOKEN or obtain an anonymous token via the documented API), creating sessions, streaming SSE, uploading files, and starting renders — all within the service domain. The skill also instructs the agent to derive and include attribution headers and to detect platform from install paths; that requires reading or inferring local install path information (a small scope expansion) but is still tied to telemetry/attribution, not unrelated data exfiltration.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing will be written to disk by an installer step. This is the lowest-risk install profile.

Credentials

Only NEMO_TOKEN is declared as required and is a reasonable credential for a remote video API. However, SKILL.md references config path(s) and platform-detection via install paths (~/.clawhub/, ~/.cursor/skills/), which implies the agent may read local path information to set headers; this is a limited additional access that should be acceptable but worth noting.

Persistence & Privilege

The skill does not request always:true or other elevated persistence, and it does not declare modifications to other skills or system-wide settings. Model invocation permissions are default and expected.

Assessment

This skill appears to do what it says: it connects to a nemo-video backend using a NEMO_TOKEN and implements session, upload, SSE streaming, and render endpoints. Before installing: (1) don't hand over a long-lived/high-privilege token unless you trust the nemo endpoint — prefer using a limited or ephemeral token; (2) the skill can obtain an anonymous token by contacting https://mega-api-prod.nemovideo.ai — be aware this contacts an external service and issues a token with limited credits; (3) the SKILL.md suggests deriving an X-Skill-Platform header by inspecting install paths (reads local path info) — if you want to avoid any filesystem probing, run the skill in an environment that prevents such access or remove that behavior; (4) monitor network usage and review the external domain before providing credentials. The only notable inconsistency is a configPath mentioned in SKILL.md that isn't reflected in the registry metadata — ask the author to clarify why that path is needed if you require an explicit audit.

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 video creation.

Try saying:

• "generate a 150-word product description into a 1080p MP4"
• "turn this script into a 60-second promo video with stock footage and music"
• "generating videos from text scripts without manual editing for marketers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free Video Generator Like InVideo — Create Videos From Text Scripts

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

A quick example: upload a 150-word product description, type "turn this script into a 60-second promo video with stock footage and music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter scripts under 100 words produce faster and more focused videos.

Matching Input to Actions

User prompts referencing free video generator like invideo, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-video-generator-like-invideo, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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.

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 a 60-second promo video with stock footage and music" — 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.

Common Workflows

Quick edit: Upload → "turn this script into a 60-second promo video with stock footage and music" → 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.