Maker Generation Generator

v1.0.0

Turn a short text description or a 30-second raw clip into 1080p generated video files just by typing what you need. Whether it's generating ready-to-share v...

0· 44·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vcarolxhberger/maker-generation-generator.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Maker Generation Generator" (vcarolxhberger/maker-generation-generator) from ClawHub.
Skill page: https://clawhub.ai/vcarolxhberger/maker-generation-generator
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install maker-generation-generator

ClawHub CLI

Package manager switcher

npx clawhub@latest install maker-generation-generator
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill is a cloud video-generation frontend and requires a single API token (NEMO_TOKEN), which is appropriate. Minor inconsistency: the registry metadata reported no required config paths, but the SKILL.md frontmatter claims a config path (~/.config/nemovideo/). This is plausibly benign (a documentation/metadata mismatch) but should be clarified.
Instruction Scope
Instructions stay within the expected scope (create/session, SSE for generation, upload/download/export workflows). Two items to watch: (1) the skill derives X-Skill-Platform from local install paths (e.g., checking ~/.clawhub/ or ~/.cursor/skills/) which implies probing the local filesystem for those paths; (2) upload semantics describe reading local file paths (multipart @/path) which is expected for uploads but means the agent will access files the user points it to. The SKILL.md also instructs obtaining an anonymous token if none exists — reasonable but be aware this issues a bearer token with limited credits.
Install Mechanism
No install steps or external packages are requested (instruction-only skill), so there is no additional install risk.
Credentials
Only a single credential (NEMO_TOKEN) is declared as required and is used directly for API auth, which matches the skill's cloud-backend purpose. The SKILL.md describes creating an anonymous token when none is present; this is consistent but the skill may persist or use that token for subsequent requests — confirm whether tokens are stored and where (env vs config path).
Persistence & Privilege
The skill is not always-enabled and makes no requests to modify other skills or global agent config in the instructions. It does reference a config directory (~/.config/nemovideo/) in frontmatter, but no explicit instructions to modify system-wide settings were found.
Assessment
This skill appears to do what it says: it talks to nemovideo.ai with a single token (NEMO_TOKEN) to create sessions, upload media, and export generated videos. Before installing or using it, confirm: (1) whether you want the agent to probe your filesystem for install-path detection (the skill uses local path checks to set an X-Skill-Platform header), (2) whether anonymous tokens obtained by the skill will be persisted to disk or environment and where (the frontmatter references ~/.config/nemovideo/), and (3) that you only upload media you intend to send to an external service. If any of those behaviors are unacceptable, ask the skill author to clarify how tokens and config are stored and to avoid silent filesystem probing.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97ds4428pem9pp92hsfq7cm0x85m0nw
44downloads
0stars
1versions
Updated 20h ago
v1.0.0
MIT-0

Getting Started

Got text prompts or clips 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 or a 30-second raw clip into a 1080p MP4"
  • "generate a 60-second video from my product description with background music"
  • "generating ready-to-share videos from text or media inputs for content creators and marketers"

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.

Maker Generation Generator — Generate Videos from Your Content

This tool takes your text prompts or clips 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 or a 30-second raw clip and want to generate a 60-second video from my product description with background music — 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 maker generation generator, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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 maker-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.

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.

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend saysYou 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 Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Common Workflows

Quick edit: Upload → "generate a 60-second video from my product description with background music" → 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 60-second video from my product description with background music" — 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.

Comments

Loading comments...