Envato Free Video Generation

Turn a product description and three brand images into 1080p ready-to-use videos just by typing what you need. Whether it's generating polished videos from i...

Security Scan

The skill's instructions and required NEMO_TOKEN are coherent with a NemoVideo cloud API, but the skill name (Envato...) appears misleading and the skill will obtain/use tokens and make network calls to an external API — verify provenance before installing or providing credentials.

Purpose & Capability

The skill's runtime instructions target the NemoVideo API (mega-api-prod.nemovideo.ai) and require a NEMO_TOKEN — that is coherent with a NemoVideo client. However the skill is named 'Envato Free Video Generation', which suggests affiliation with Envato but no Envato endpoints, credentials, or APIs are used or requested. The naming/branding mismatch is misleading and could be deceptive to users.

Instruction Scope

SKILL.md confines actions to interacting with the described remote API: creating/using a session, uploading files, streaming SSE, checking credits, and starting renders. It instructs how to obtain an anonymous token if NEMO_TOKEN is absent. It does not instruct reading unrelated local files or unrelated environment variables (aside from possibly detecting install path to set an attribution header).

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so it writes nothing to disk and does not download external installers. That is the lowest-risk install mechanism.

Credentials

The skill requests a single credential, NEMO_TOKEN, which matches the API it uses. There are no other unrelated secrets or config paths requested. The flow to obtain an anonymous token if none is provided is documented in the instructions.

Persistence & Privilege

The skill is not always-on and does not request elevated platform privileges. Autonomous model invocation is enabled (default) but not combined with other red flags. Nothing in the instructions indicates it modifies other skills or global agent settings.

What to consider before installing

This skill appears to be a client for the NemoVideo API but is labeled as 'Envato', which is misleading and worth questioning. Before installing: (1) confirm the skill publisher and whether it truly represents Envato or a third party; (2) avoid pasting high-privilege or long-lived credentials — prefer letting the skill get an anonymous starter token if you don't have a vetted NEMO_TOKEN; (3) be aware the skill will upload your images/audio to mega-api-prod.nemovideo.ai and will include attribution headers; (4) review the NemoVideo service's privacy, billing and terms (uploads may be stored/processed); (5) if you need stronger assurance, ask the publisher to clarify the Envato naming or provide an official affiliation statement and/or a trustworthy homepage or source repository. Additional info that would raise confidence: an author/homepage that confirms the Envato affiliation or explicit statement that this is an independent tool (not affiliated), and documentation showing the NEMO_TOKEN scope and lifetime.

Getting Started

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

Try saying:

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

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.

Envato Free Video Generation — Generate Videos Without Paid Assets

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

Say you have a product description and three brand images and want to generate a 30-second promo video from my product photos and tagline — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using high-contrast images as inputs produces cleaner transitions in the final video.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is envato-free-video-generation, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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

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

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.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

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)

Common Workflows

Quick edit: Upload → "generate a 30-second promo video from my product photos and tagline" → 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 "generate a 30-second promo video from my product photos and tagline" — 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 browsers.