How To Create Ai Videos For Free

generate text or images into ready-to-share videos with this skill. Works with MP4, JPG, PNG, TXT files up to 200MB. content creators use it for generating A...

Security Scan

The skill's instructions largely match a video-generation API workflow, but there are small inconsistencies (undeclared config path in the skill metadata) and a lack of provenance that warrant caution before installing or providing credentials.

Purpose & Capability

The name/description match the runtime instructions: the SKILL.md shows a clear workflow for sending text/images to a remote nemo-video API and getting MP4s back. Requiring a single NEMO_TOKEN is proportionate. However, the frontmatter metadata also lists a config path (~/.config/nemovideo/) while the registry metadata said "Required config paths: none" — that mismatch is unexplained and should be clarified.

Instruction Scope

Instructions are narrowly scoped to establishing a session, sending SSE messages, uploading files, polling session state, and exporting renders. They explicitly instruct use of Authorization headers, attribution headers, and uploading user-supplied files. There are no instructions to read unrelated system files or other environment variables. The only scope concern is the expectation to access a local config path (see above) implied in the frontmatter.

Install Mechanism

This is an instruction-only skill with no install spec or code files — lowest-risk install mechanism. No downloads, package installs, or binaries are requested.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which is appropriate for a third-party API. The SKILL.md also describes obtaining an anonymous token via the API if no env var is present (ephemeral). The metadata's reference to ~/.config/nemovideo/ is not declared elsewhere in the registry and could imply local config access; that is not justified in the top-level manifest and should be clarified.

Persistence & Privilege

always:false and no claims to modify other skills or system-wide settings. The skill may create or use a session on the remote service but does not request persistent platform privileges. The only persistence concern is the metadata's implied local config path which could be used for storing tokens if implemented — this is not declared in registry-level fields.

What to consider before installing

This skill appears to implement a reasonable workflow for a third-party video-generation API and asks only for a single API token (NEMO_TOKEN). Before installing, consider: 1) provenance — the skill has no homepage or known source; verify the domain (mega-api-prod.nemovideo.ai) and whether you trust that service. 2) Tokens — if you supply NEMO_TOKEN it will be sent as a Bearer token on every request; do not supply high-privilege or multi-service credentials. 3) Local config path mismatch — the SKILL.md metadata references ~/.config/nemovideo/ but the registry said no config paths; ask the publisher to explain whether the skill will read or write that directory. 4) Data exposure — uploaded files (images, text, or local file paths) and generated media are sent to the remote API; don't send sensitive content you wouldn't want shared with that service. If the publisher can provide a homepage, privacy policy, or clarify the config-path usage, the assessment could be upgraded to benign.

Getting Started

Got text or images to work with? Send it over and tell me what you need — I'll take care of the AI video generation.

Try saying:

• "generate a short text script or three product images into a 1080p MP4"
• "create a 30-second promotional video from my product description"
• "generating AI 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.

How to Create AI Videos for Free — Generate Videos from Text or Images

Drop your text or images 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 script or three product images, ask for create a 30-second promotional video from my product description, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter scripts under 60 words generate faster and more accurately.

Matching Input to Actions

User prompts referencing how to create ai videos for 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	how-to-create-ai-videos-for-free
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.

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.

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 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 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 → "create a 30-second promotional video from my product description" → 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 "create a 30-second promotional video from my product description" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.