Free Video Generation Ai Tools

Skip the learning curve of professional editing software. Describe what you want — generate a 30-second video from my product description with background mus...

Security Scan

The skill appears to perform cloud video generation as described, but there are inconsistencies between its declared requirements and its runtime instructions (token handling, config path metadata, and a directive to hide technical details), so proceed with caution.

Purpose & Capability

The name/description match the runtime actions (upload media, call a cloud video-render API). Requesting a single NEMO_TOKEN credential is reasonable for this service. However, the registry metadata lists no config paths while the skill's frontmatter metadata includes a config path (~/.config/nemovideo/), and the skill declares NEMO_TOKEN as required even though the SKILL.md provides an anonymous-token flow if NEMO_TOKEN is absent. Also the headers require detecting an install path (X-Skill-Platform) despite the skill being instruction-only with no install spec. These mismatches are incoherent and worth clarifying.

Instruction Scope

Instructions explicitly direct network activity to https://mega-api-prod.nemovideo.ai (session creation, SSE, uploads, exports) and to upload user files up to 200MB — all consistent with purpose. Concerningly, the skill tells the agent to 'Keep the technical details out of the chat', which encourages hiding implementation details (including token acquisition and API interaction) from the user. The instructions also require setting specific attribution headers on every request. No instructions ask for unrelated system files, but the frontmatter's config path suggests possible local config access which is not documented in the runtime steps.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be written to disk by an installer. That minimizes installation risk.

Credentials

The only declared environment credential is NEMO_TOKEN, which is appropriate for a service token. But SKILL.md provides an alternate anonymous-token acquisition flow when NEMO_TOKEN is absent, so marking NEMO_TOKEN as strictly required in the registry is inconsistent. The frontmatter also references a config path (~/.config/nemovideo/) that could imply reading local stored tokens or config; the registry summary did not list that path. These discrepancies mean it's unclear whether the skill will read local config and/or require a long-lived token, raising privacy/credential concerns.

Persistence & Privilege

The skill does not request always:true or other elevated platform privileges. It does not declare modifications to other skills or system-wide settings. Autonomous invocation is allowed (platform default), which combined with the other concerns increases blast radius, but the skill itself does not request persistent platform privileges.

What to consider before installing

This skill likely does what it says (calls a cloud API to generate videos), but there are red flags you should address before installing: 1) Confirm the source and trustworthiness of https://mega-api-prod.nemovideo.ai — the skill has no homepage or known owner. 2) Ask the author to resolve metadata inconsistencies: either remove the configPath from the frontmatter or document why ~/.config/nemovideo/ is needed, and clarify whether NEMO_TOKEN is optional (anonymous-token flow) or required. 3) Avoid providing long‑lived or highly privileged credentials — prefer an ephemeral or scoped token. 4) Be cautious about uploading sensitive files (the skill asks to upload up to 200MB). 5) The skill instructs the agent to 'keep technical details out of the chat' — insist on transparency about token usage, where tokens are stored, and what the agent will disclose to you. 6) If you test it, try with non-sensitive sample media and an ephemeral token. If the vendor is unknown, consider rejecting or sandboxing the skill until the above questions are answered.

Getting Started

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

Try saying:

• "generate my text prompts or images"
• "export 1080p MP4"
• "generate a 30-second video from my"

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.

Free Video Generation AI Tools — Generate Videos from Text Prompts

This tool takes your text prompts or images and runs AI video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a short text description like 'a sunset over the ocean with calm waves' and want to generate a 30-second video from my product description with background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter and more specific prompts produce more accurate video results.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Header	Value
X-Skill-Source	free-video-generation-ai-tools
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.

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)

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

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.

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 30-second video from my product description with background music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and devices.

Common Workflows

Quick edit: Upload → "generate a 30-second video from my product description with background 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.