Create A Free Ai Video

create text or images into AI generated videos with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. content creators and marketers use it for ge...

Security Scan

The skill's declared requirements and runtime instructions are broadly consistent with a cloud-based AI video creation service, but there are a few minor mismatches and privacy/networking considerations you should confirm before installing.

Purpose & Capability

Name/description match the instructions and API endpoints (video generation, uploads, exports). The skill declares NEMO_TOKEN as the primary credential which fits a remote API. Minor inconsistency: metadata lists a config path (~/.config/nemovideo/) even though the SKILL.md does not require reading that path or other local configs.

Instruction Scope

SKILL.md stays within the stated purpose (session creation, SSE-driven generation, uploads, polling for renders). It instructs the agent to auto-obtain an anonymous token if NEMO_TOKEN is absent and to store session_id/token for subsequent calls. It also asks to auto-detect the 'install path' to set an X-Skill-Platform header — that may require reading agent/installation paths and should be clarified. The skill asks the agent to upload files by path or URL (expected) but does not instruct reading unrelated files or environment variables.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest risk from installation. All runtime behavior happens via network calls to the external API.

Credentials

Only NEMO_TOKEN is declared as required, which is proportionate for an API client. The SKILL.md will generate an anonymous token automatically if none is provided (reasonable). The presence of a declared config path (~/.config/nemovideo/) is unexplained by the instructions and should be clarified. No other credentials are requested.

Persistence & Privilege

The skill is not always-enabled and does not request elevated system privileges. It instructs storing session_id and token for the session but does not explicitly ask to modify system-wide configs or other skills. Confirm where tokens/sessions are persisted (in-memory vs written to disk).

Assessment

This skill appears to do what it claims: it talks to a nemo-video API to create videos and needs a NEMO_TOKEN (it can acquire an anonymous one itself). Before installing, confirm the following: 1) Trustworthiness of the external domain (mega-api-prod.nemovideo.ai) — uploaded files and prompts will be sent there, so do not upload sensitive personal or corporate data. 2) Where the anonymous token and session_id are stored (in-memory vs written to ~/.config or other disk paths); the frontmatter lists a config path that the instructions never reference — ask the author to clarify. 3) Whether the agent will read the agent install path or other local filesystem locations to populate the X-Skill-Platform header — that may expose metadata about your environment. If those points are acceptable, the skill is internally consistent. If you need higher assurance, request the skill author provide a privacy/data-retention statement and clarify persistence/storage behavior.

Getting Started

Ready when you are. Drop your text or images here or describe what you want to make.

Try saying:

• "create a short product description and three brand photos into a 1080p MP4"
• "turn my text and images into a 30-second promotional video"
• "generating videos from text prompts or images without filming for content creators and marketers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Create a Free AI Video — Generate Videos from Text or Images

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 product description and three brand photos, type "turn my text and images into a 30-second promotional video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter scripts with clear prompts produce more accurate results.

Matching Input to Actions

User prompts referencing create a free ai video, 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	create-a-free-ai-video
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 → "turn my text and images into a 30-second promotional video" → 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 text and images into a 30-second promotional video" — 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 across social platforms.