Ai Video Generatore Gratis

Skip the learning curve of professional editing software. Describe what you want — crea un video promozionale di 30 secondi con musica e testo — and get read...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based AI video generation service: it needs a NEMO_TOKEN (or will obtain an anonymous one), uploads user media to a remote API, and has no install step or unrelated credential requests.

Purpose & Capability

Name/description (AI video generation) match the declared environment requirement (NEMO_TOKEN) and the SKILL.md which describes a remote rendering API. The declared config path (~/.config/nemovideo/) is consistent with a client for a service called 'nemovideo'. No unrelated services or credentials are requested.

Instruction Scope

SKILL.md instructs the agent to check NEMO_TOKEN, otherwise generate a UUID and call an anonymous-token endpoint to obtain a short-lived NEMO_TOKEN, create sessions, upload user files (multipart or URL), stream SSE messages, and poll render endpoints. All of these actions are coherent for a cloud render pipeline, but they will transmit user media and session tokens to https://mega-api-prod.nemovideo.ai — users should expect that uploaded files and session metadata leave the local environment.

Install Mechanism

No install spec and no code files are present, so nothing is written to disk by an installer. This is the lowest-risk model for an integration that relies on making HTTP calls to a remote service.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv). The skill will generate an anonymous token if none is provided; that behavior is documented in SKILL.md. The single env var and optional config path are proportionate to a cloud video service, but users should be aware that providing NEMO_TOKEN gives the skill bearer access to the service on the user's behalf and that anonymous tokens can be obtained automatically.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It does not modify other skills or system-wide settings. Session tokens are short-lived per the instructions (anonymous tokens expire after 7 days).

Assessment

This skill appears to do what it says — generate videos via a remote service — but it will upload your images/clips and use a service token (NEMO_TOKEN) or create an anonymous token for you. Before installing or using it: (1) confirm you are comfortable uploading the media you plan to use to the external domain (mega-api-prod.nemovideo.ai); (2) only provide NEMO_TOKEN if you trust that provider (the token grants the skill access to your account/credits); (3) avoid uploading sensitive/private files unless you’ve reviewed the provider’s privacy/security policies; (4) note anonymous tokens expire in ~7 days and are rate-limited; and (5) if you want to limit outbound calls, do not install or provide a token. Overall the skill is internally consistent, but exercise normal caution about sending data to external services.

Getting Started

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

Try saying:

• "generate five product images and a logo file into a 1080p MP4"
• "crea un video promozionale di 30 secondi con musica e testo"
• "generating videos from images or clips for free for content creators and small business owners"

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.

AI Video Generatore Gratis — Generate Videos Free with AI

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

Say you have five product images and a logo file and want to crea un video promozionale di 30 secondi con musica e testo — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using fewer images speeds up generation significantly.

Matching Input to Actions

User prompts referencing ai video generatore gratis, 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

Header	Value
X-Skill-Source	ai-video-generatore-gratis
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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

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.

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)

Common Workflows

Quick edit: Upload → "crea un video promozionale di 30 secondi con musica e testo" → 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 "crea un video promozionale di 30 secondi con musica e testo" — 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.