Ai Video Generator Free Me

Get ready-to-share videos ready to post, without touching a single slider. Upload your text or images (MP4, MOV, JPG, PNG, up to 200MB), say something like "...

Security Scan

The skill's requirements and runtime instructions are internally consistent with its stated purpose (remote AI video generation); it only asks for a single service token and uses an API for session, upload, SSE and export workflows, though there are a few minor notes to double-check before installing.

Purpose & Capability

Name/description (generate videos from text/images) matches the declared requirement (NEMO_TOKEN) and the API endpoints described in SKILL.md. No unrelated cloud providers or unrelated credentials are requested.

Instruction Scope

Instructions are focused on connecting to the remote nemovideo API, creating a session, streaming SSE, uploading files, polling export status, and returning download URLs. They do request reading this skill's YAML frontmatter for attribution and detecting install path (~/.clawhub, ~/.cursor/skills/) — which implies reading some local paths; verify it only reads its own metadata and not arbitrary user files.

Install Mechanism

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

Credentials

Only a single credential (NEMO_TOKEN) is declared as required and used as a bearer token for the service — proportional to the skill's purpose. The skill also instructs how to obtain an anonymous starter token via the service API if NEMO_TOKEN is absent. The metadata lists a config path (~/.config/nemovideo/); confirm whether the skill actually needs to read that path and that it won't access unrelated user secrets.

Persistence & Privilege

always is false and the skill does not request elevated or persistent system privileges. It does not attempt to modify other skills or system-wide agent settings.

Assessment

This skill appears coherent for generating videos via the named backend, but take these precautions before installing or using it: 1) Only provide a NEMO_TOKEN you trust — prefer an account-scoped or short-lived token; if possible use the anonymous token flow for untrusted use. 2) Confirm the API base (https://mega-api-prod.nemovideo.ai) is the official service you expect; if unknown, review the service privacy/security policies. 3) The skill may read its own frontmatter and detect an install path — ensure it does not read arbitrary user files or secrets (e.g., ~/.ssh, other config directories). 4) Avoid uploading sensitive content (private keys, PII) because uploads are sent to a remote GPU service. 5) If you need stronger assurance, run the skill in a sandboxed environment, monitor outbound requests, or ask the publisher for source code or a trustworthy homepage. If you want, I can suggest specific checks or a minimal test prompt to validate behavior safely.

Getting Started

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

Try saying:

• "generate a short text script or three product photos into a 1080p MP4"
• "turn my script into a 60-second video with visuals and music"
• "generating videos from text or images for free 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.

AI Video Generator Free — Generate Videos From Text Free

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

Worth noting: shorter scripts generate faster and give cleaner results.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: ai-video-generator-free-me
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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

Common Workflows

Quick edit: Upload → "turn my script into a 60-second video with visuals 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my script into a 60-second video with visuals and music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.