Video Generator Free Simple

generate text or images into ready-to-share videos with this skill. Works with MP4, JPG, PNG, MOV files up to 200MB. beginners and casual creators use it for...

Security Scan

The skill's behavior largely matches a cloud video-generation service, but there are inconsistencies about required credentials and local config/storage that warrant caution before installing or uploading private media.

Purpose & Capability

The name/description describe cloud video generation from text/images and the SKILL.md instructs API calls for uploads, rendering, and exports — this is coherent. Minor mismatch: registry metadata initially lists no config paths, but the SKILL.md frontmatter declares ~/.config/nemovideo/ as a config path.

Instruction Scope

Instructions stay within the expected surface: call the nemovideo API, upload user-provided media, manage session and render jobs, handle SSE. They do not instruct reading unrelated system files or other credentials. They do instruct saving session/token data locally (implied config path).

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install model.

Credentials

The skill declares NEMO_TOKEN as the required/primary env var, which makes sense for an API client. However, the SKILL.md also describes creating an anonymous token via the API if NEMO_TOKEN is not present — meaning NEMO_TOKEN is effectively optional. That mismatch (declared required but optional in practice) and the implicit local token/session storage (config path) are inconsistent and should be clarified before use.

Persistence & Privilege

The skill implies writing session/credential data to ~/.config/nemovideo/ (frontmatter), which is local persistence but scoped to its own config path. Registry metadata elsewhere does not list this path, so verify whether the skill will create or modify files there. always:true is not set and autonomous invocation is normal.

What to consider before installing

This skill sends any uploaded media and requests to https://mega-api-prod.nemovideo.ai and uses an API token (NEMO_TOKEN). Before installing or using it: 1) Confirm you trust the remote domain and owner (no homepage provided). 2) Understand that your media will be uploaded to that service — do not upload sensitive or private data unless you accept that risk. 3) Clarify the NEMO_TOKEN behavior: the skill declares it as required but can create an anonymous token itself; ask whether you want to supply your own token or allow the skill to obtain one. 4) Confirm whether the skill will write session/token files to ~/.config/nemovideo/ (and inspect those files if desired). 5) If concerned, test with non-sensitive files or use a separate account/ephemeral environment. The inconsistencies noted (required vs optional token and mismatched config-path metadata) are the main reason this is flagged as suspicious rather than benign.

Getting Started

Share your text or images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "generate my text or images"
• "export 1080p MP4"
• "create a 30-second video from my"

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 Generator Free Simple — Create and Export Videos Fast

Drop your text or images in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short text description or three product images, ask for create a 30-second video from my product photos with background music, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter scripts and fewer images generate faster results.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-generator-free-simple
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

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.

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 30-second video from my product photos with background music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "create a 30-second video from my product photos with background music" → Download MP4. Takes 30-60 seconds 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.