Free Generator Generation

Get AI generated videos ready to post, without touching a single slider. Upload your text prompts (MP4, MOV, WebM, AVI, up to 500MB), say something like "gen...

Security Scan

The skill's requirements and instructions align with a cloud video-generation service; nothing obvious is asking for unrelated credentials or installing code, but it will upload your files to an external API and has a small metadata inconsistency you should note.

Purpose & Capability

The name/description describe a cloud AI video-generation service and the skill only requests NEMO_TOKEN (the service token) and uses HTTP APIs for upload/rendering — this is coherent. Minor inconsistency: the SKILL.md YAML frontmatter includes a configPaths entry (~/.config/nemovideo/) even though the registry metadata lists no required config paths; that mismatch should be clarified.

Instruction Scope

Runtime instructions stay within video generation: create a session, send SSE messages, upload files, poll render status, and return download URLs. The skill tells the agent to auto-acquire an anonymous token if NEMO_TOKEN is absent and to detect install path to set X-Skill-Platform headers. These are expected for the described service, but the agent will be instructed to upload user files to an external domain and to look for an optional local config path mentioned in the frontmatter.

Install Mechanism

No install spec or code is present — instruction-only skills have lower risk because nothing is written to disk by the skill itself.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv) which is proportionate for a cloud API. The SKILL.md also references a local config path (~/.config/nemovideo/) in its frontmatter, which wasn't declared elsewhere; otherwise no unrelated secrets or broad credential access are requested.

Persistence & Privilege

The skill is not always-enabled, does not request elevated or system-wide changes, and does not attempt to modify other skills. It is allowed to be invoked autonomously by default (platform normal), which expands its runtime reach but is expected for skills.

Assessment

This skill looks like what it claims: it will upload media and text to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (or obtain a short-lived anonymous token) to create sessions, render jobs, and return a download URL. Before installing, consider: only upload media you are comfortable sending to an external service; make sure you trust nemo video's domain (no homepage was provided); if you want to avoid automatic credential borrowing, do not set NEMO_TOKEN and review the anonymous-token behavior; ask the publisher to clarify the YAML frontmatter configPaths (~/.config/nemovideo/) vs. the registry metadata mismatch if you care about local config reads.

Getting Started

Got text prompts to work with? Send it over and tell me what you need — I'll take care of the AI video generation.

Try saying:

• "generate a short text description of a product demo scene into a 1080p MP4"
• "generate a 30-second video from this script about a coffee brand launch"
• "generating videos from text prompts at no cost for content creators"

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 Generator Generation — Generate Videos From Text Free

This tool takes your text prompts 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 of a product demo scene and want to generate a 30-second video from this script about a coffee brand launch — 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 generator 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-generator-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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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.

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.

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

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 → "generate a 30-second video from this script about a coffee brand launch" → 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 video from this script about a coffee brand launch" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, WebM, AVI for the smoothest experience.

Export as MP4 for widest compatibility.