Video Generator Free Models

generate text prompts into AI generated videos with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. content creators use it for generating shor...

Security Scan

The skill's behavior is broadly consistent with a cloud video-generation integration, but there are several inconsistencies and small scope-creep details (token handling fallback, hidden/internal tool results, metadata mismatch) you should understand before installing.

Purpose & Capability

The name/description match the runtime instructions: the skill talks to a nemo video-generation API, uploads media, starts render jobs and returns download URLs. Requesting a NEMO_TOKEN credential is expected for this purpose.

Instruction Scope

Instructions are narrowly focused on calling the external API, SSE handling, upload/export flows and polling render status. Two noteworthy items: (1) if NEMO_TOKEN is absent the instructions tell the agent to automatically obtain an anonymous token from the remote API and use it as NEMO_TOKEN, and (2) SSE/tool call results are marked 'process internally, don't forward' which intentionally hides some backend interactions from the user. Both behaviors merit caution.

Install Mechanism

No install spec or code files — instruction-only skill. This is the lowest-risk install model (no archives downloaded or binaries created).

Credentials

Only one credential is declared (NEMO_TOKEN) which is proportional to a hosted-video API. However, the SKILL.md also documents a fallback to auto-fetch an anonymous token and use it as NEMO_TOKEN — that conflicts with the 'required env var' expectation and means the agent may create/store/use tokens on the fly.

Persistence & Privilege

Skill does not request always:true, does not modify other skills, and has no install-time persistence. It does rely on session tokens for queued render jobs (expected) which could orphan jobs if a client disconnects.

What to consider before installing

This skill talks to a third-party API (mega-api-prod.nemovideo.ai) to upload files and render videos. Before installing: (1) confirm you trust that domain and the service operator, (2) avoid putting long-lived, high-privilege secrets in NEMO_TOKEN unless you understand its scope — the skill can also obtain anonymous tokens itself, (3) be aware you will be uploading media (local file paths may be sent to the API) and some backend interactions are indicated as 'process internally, don't forward' so not all activity is surfaced to the user, and (4) note a minor metadata inconsistency in the skill frontmatter (it references a config path) — ask the publisher to clarify how tokens/session data are stored and whether any local config is read before using it. If you need higher assurance, ask the author for an explicit privacy/security statement and whether the anonymous token flow stores any identifying data.

Getting Started

Send me your text prompts and I'll handle the AI video generation. Or just describe what you're after.

Try saying:

• "generate a short text description of a sunset over the ocean into a 1080p MP4"
• "generate a 15-second video clip of a forest with birds flying overhead"
• "generating short videos from text prompts using free AI models for content creators"

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.

Video Generator Free Models — Generate Videos From Text Free

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

Here's a typical use: you send a a short text description of a sunset over the ocean, ask for generate a 15-second video clip of a forest with birds flying overhead, and about 1-3 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter and more specific prompts tend to produce more accurate video results.

Matching Input to Actions

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

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

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 15-second video clip of a forest with birds flying overhead" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "generate a 15-second video clip of a forest with birds flying overhead" → Download MP4. Takes 1-3 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.