Free Generation Generator

generate text prompts into generated video clips with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. content creators use it for generating vi...

Security Scan

The skill's behavior mostly matches a text→video service, but there are a few inconsistencies and privacy implications you should understand before installing.

Purpose & Capability

The skill claims to convert text prompts into videos and its runtime instructions call a video-rendering backend (mega-api-prod.nemovideo.ai) with endpoints for session, SSE-based edits, uploads, exports and credits. The single declared credential (NEMO_TOKEN) fits that purpose.

Instruction Scope

SKILL.md instructs the agent to automatically obtain an anonymous token (POST to /api/auth/anonymous-token) when NEMO_TOKEN is absent, create and store a session_id, upload user files, poll export endpoints, and keep raw token/API responses hidden from users. These actions are consistent with the stated purpose, but they mean user prompts and uploaded media will be sent to an external service and a token will be created/stored on the host. The instructions also describe detecting the install path to set an X-Skill-Platform header, which implies the agent may probe filesystem paths — not strictly required for core functionality.

Install Mechanism

There is no install spec and no code files (instruction-only). This minimizes installation risk because nothing is downloaded or written by the skill itself. Runtime network calls to the external backend are the main surface.

Credentials

Only NEMO_TOKEN is required, which is appropriate. However, the SKILL.md frontmatter also references a config path (~/.config/nemovideo/) while the registry metadata showed no required config paths — an inconsistency. The skill will create/obtain and store an anonymous token if none is present; that token is bearer-style and will be sent on every request. Users should treat that token and any uploaded files as sensitive because they will be transmitted to the external service.

Persistence & Privilege

always is false and there are no install-time actions or claims to modify other skills or system-wide settings. The skill expects to store a session_id and possibly cached token information for subsequent calls, which is normal for a networked service integration.

What to consider before installing

This skill will send your prompts and any uploaded media (videos, images, audio) to mega-api-prod.nemovideo.ai and will obtain/store a bearer token (NEMO_TOKEN) automatically if you don't supply one. Before installing or using it: 1) Confirm you trust the external service and are comfortable having files and prompts transmitted there (no homepage or official source is provided in the registry). 2) Note the SKILL.md references storing data under ~/.config/nemovideo/ (the registry metadata omitted this) — check where tokens/session IDs will be kept and whether you can delete them. 3) If you have sensitive content, avoid uploading it; revoke any anonymous token or delete stored session/config files after use if possible. 4) If you want stronger assurance, ask the publisher for a homepage/privacy policy or an auditable implementation (code) so you can verify exactly what is stored and transmitted.

Getting Started

Ready when you are. Drop your text prompts here or describe what you want to make.

Try saying:

• "generate a short text description of a beach sunset scene into a 1080p MP4"
• "generate a 30-second video clip from my text prompt at no cost"
• "generating videos from text prompts for free for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free Generation Generator — Generate Videos From Text Free

Drop your text prompts in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short text description of a beach sunset scene, ask for generate a 30-second video clip from my text prompt at no cost, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter, more specific prompts produce better results than vague descriptions.

Matching Input to Actions

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

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

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)

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second video clip from my text prompt at no cost" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a 30-second video clip from my text prompt at no cost" → 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.