Meta Ai Video Generator Free

Get AI-generated videos ready to post, without touching a single slider. Upload your images or clips (MP4, MOV, JPG, PNG, up to 500MB), say something like "t...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based AI video generator: it only needs a single service token and uses remote APIs to upload media and render videos, with no unexpected credential or install requests.

Purpose & Capability

The name/description describe a cloud video-generation service and the skill only requests a single service token (NEMO_TOKEN) and remote API calls to mega-api-prod.nemovideo.ai — these are consistent with the stated purpose. Minor metadata discrepancy: the skill frontmatter advertises a config path (~/.config/nemovideo/) while registry metadata lists no required config paths, which is inconsistent but not inherently malicious.

Instruction Scope

SKILL.md instructs the agent to check for NEMO_TOKEN, create an anonymous token via the provider's auth endpoint if missing, create and maintain a session_id, upload files (multipart or URL), stream SSE responses, and poll render status. These actions stay within the expected scope for a remote-rendering video generator. Notes: uploads require reading user-supplied files (expected), and the skill asks callers to auto-detect an install path for X-Skill-Platform which may require access to agent install metadata — this is implementation detail but worth awareness.

Install Mechanism

There is no install spec and no code to write to disk (instruction-only), which is the lowest-risk install mechanism. Nothing is downloaded or extracted by the skill itself.

Credentials

Only one credential is declared (NEMO_TOKEN) and the SKILL.md uses only that token for Bearer auth. That is proportionate for a service that performs authenticated API calls. The frontmatter's configPaths entry is inconsistent with registry metadata and suggests possible local config storage, which should be clarified before trusting persistent storage.

Persistence & Privilege

The skill is not marked always:true and does not request elevated privileges. It will keep an in-session session_id and uses tokens; SKILL.md does not explicitly instruct writing tokens to disk, but frontmatter references a config path (~/.config/nemovideo/) which implies possible persistence. Confirm whether tokens/session state are persisted locally and where.

Assessment

This skill appears to do what it says, but review a few things before installing: 1) Confirm you trust the backend domain (mega-api-prod.nemovideo.ai) because all uploads and rendering happen there — your media will leave your machine. 2) Decide whether you want the skill to auto-create a NEMO_TOKEN (it will POST to the provider to get an anonymous token) or supply your own token to avoid anonymous account creation. 3) Ask the maintainer whether tokens or session state are persisted under ~/.config/nemovideo/ (frontmatter mentions this but registry metadata did not); if you prefer no local persistence, confirm where state is stored. 4) If you care about privacy/retention or credit usage, review the provider's terms and the API responses. None of the current instructions request unrelated credentials or perform suspicious filesystem access, but confirming the above will reduce risk.

Getting Started

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

Try saying:

• "generate my images or clips"
• "export 1080p MP4"
• "turn my product photos into a"

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.

Meta AI Video Generator Free — Generate Videos from Images Free

Send me your images or clips 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 five product images or a short 30-second clip, type "turn my product photos into a promotional video with music and transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: using fewer than 10 images speeds up generation significantly.

Matching Input to Actions

User prompts referencing meta ai video generator free, 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	meta-ai-video-generator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-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.

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)

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 "turn my product photos into a promotional video with music and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "turn my product photos into a promotional video with 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.