Ai Video Generator Free Envato

Turn five product images and a logo file into 1080p ready-to-use videos just by typing what you need. Whether it's generating polished videos from images or...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a remote AI video-rendering integration (it only needs a NEMO_TOKEN and uploads user media to nemo's API), but there are a few small metadata/instruction mismatches you should note before installing.

Purpose & Capability

The skill's name and description (generate videos from images) align with the runtime instructions that call a remote Nemovideo API and upload media. Minor mismatch: the registry summary above listed no required config paths, but the SKILL.md frontmatter declares a configPath (~/.config/nemovideo/). The 'Envato' mention in the display name appears to be marketing only; no Envato credentials or APIs are requested.

Instruction Scope

SKILL.md instructs the agent to use NEMO_TOKEN (or obtain an anonymous token via the specified endpoint), create sessions, upload files, send SSE messages, poll render status, and include attribution headers read from the skill's YAML frontmatter. These actions are within expected scope, but it also asks the agent to detect install path to set X-Skill-Platform (implies reading filesystem paths) and to read the file's frontmatter at runtime — both are reasonable but expand the agent's file-system access beyond strictly sending user media.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing is written to disk by an installer. Low install risk.

Credentials

Only one required environment variable (NEMO_TOKEN / primary credential), which matches the described API usage. Minor inconsistency between top-level registry 'Required config paths: none' and SKILL.md's frontmatter declaring ~/.config/nemovideo/.

Persistence & Privilege

No special persistence requested (always:false). The skill is user-invocable and may be invoked autonomously by the agent (default), which is expected for skills. The skill does not request modification of other skills or system-level config.

Assessment

This skill appears to do what it claims: it sends images/clips to a remote Nemovideo API and returns rendered videos, and it only requests a single credential (NEMO_TOKEN). Before installing, consider: - The skill will upload any media you provide to https://mega-api-prod.nemovideo.ai — do not send sensitive images or media you would not want stored/processed remotely. - You can avoid supplying a persistent token by letting the skill request an anonymous token (the skill details this flow). If you do provide a NEMO_TOKEN, use a token with limited scope/expiry if possible. - There is a small metadata mismatch: the registry said no config paths required, but the skill frontmatter references ~/.config/nemovideo/ and asks the agent to detect install path (filesystem read). If you care about limiting filesystem access, ask for clarification or refuse filesystem reads. - The skill instructs the agent not to print tokens, but you should still monitor outputs for accidental token exposure. - If you are unsure about the backend domain or the identity of 'nemovideo.ai', verify the service's legitimacy before supplying real credentials. Overall the skill is internally coherent for a remote video-rendering integration, but proceed with normal caution around uploading content and supplying API credentials.

Getting Started

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

Try saying:

• "generate my images or clips"
• "export 1080p MP4"
• "turn these images into a 30-second"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

AI Video Generator Free Envato — Generate Videos from Images Free

Send me your images or clips 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 five product images and a logo file, type "turn these images into a 30-second promotional video with music and text overlays", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: using fewer than 10 images keeps render times under a minute.

Matching Input to Actions

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

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

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

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

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 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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these images into a 30-second promotional video with music and text overlays" — 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 with Envato and social platforms.

Common Workflows

Quick edit: Upload → "turn these images into a 30-second promotional video with music and text overlays" → 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.