Text To Video Game

v1.0.0

Get game scene videos ready to post, without touching a single slider. Upload your text prompts (TXT, DOCX, PDF, PNG, up to 50MB), say something like "turn m...

⭐ 0· 69·0 current·0 all-time

by@vynbosserman65

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vynbosserman65/text-to-video-game.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Text To Video Game" (vynbosserman65/text-to-video-game) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/text-to-video-game
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 text-to-video-game

ClawHub CLI

Package manager switcher

npx clawhub@latest install text-to-video-game

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description (convert text prompts to game-scene videos) match the declared requirement (NEMO_TOKEN) and the SKILL.md, which documents calls to a nemo video API. There are no unrelated credentials or binaries requested.

✓

Instruction Scope

SKILL.md instructs the agent to obtain or use NEMO_TOKEN, create sessions, upload user media, stream SSE, and start renders — all within the scope of a cloud render service. It does not instruct collecting unrelated system secrets. One minor ambiguity: header attribution includes a platform value detected from install path (e.g. ~/.clawhub/ or ~/.cursor/skills/), which implies the agent may inspect its install path; this is plausibly for attribution and not required for core functionality.

✓

Install Mechanism

There is no install spec and no code to write to disk (instruction-only). This is the lowest-risk install profile.

✓

Credentials

Only a single service credential (NEMO_TOKEN) is required and the SKILL.md explains how to obtain an anonymous token if none exists. A declared config path (~/.config/nemovideo/) appears reasonable for storing session/token state. No unrelated secrets or multiple service keys are requested.

✓

Persistence & Privilege

The skill does not request always:true and has no install-time persistence. The agent may invoke it autonomously (platform default) but that is expected for an integration that can run API calls; no system-wide modifications are requested.

Assessment

This skill appears to do what it claims: it will upload your prompts and media to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (or an anonymous token it can fetch) to run cloud renders. Before installing, consider: (1) only provide content you are comfortable uploading to an external service; (2) verify the domain and review the service's privacy/terms if you care about IP or copyrighted content; (3) prefer setting NEMO_TOKEN as an environment variable rather than pasting tokens into chat; (4) the skill may detect its install path for attribution headers — avoid installing it in locations that reveal sensitive local info; and (5) anonymous tokens expire and exports may be gated by credits/subscription. If any of these are unacceptable, do not install or use the skill.

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

Runtime requirements

🎮 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97esep9mjsky25mfgmw5gm1b184yjg7

69downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

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

Try saying:

"generate my text prompts"
"export 1080p MP4"
"turn my game concept description into"

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.

Text to Video Game — Generate Game Scenes from Text

Send me your text prompts and describe the result you want. The AI game video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a paragraph describing a fantasy dungeon level, type "turn my game concept description into a playable-style video with characters and environment", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.

Worth noting: shorter, more specific descriptions produce more accurate game scenes.

Matching Input to Actions

User prompts referencing text to video game, 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 text-to-video-game, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with `?bind=<id>` (get `<id>` from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my game concept description into a playable-style video with characters and environment" — concrete instructions get better results.

Max file size is 50MB. Stick to TXT, DOCX, PDF, PNG for the smoothest experience.

Export as MP4 for widest compatibility with game engines and social platforms.

Common Workflows

Quick edit: Upload → "turn my game concept description into a playable-style video with characters and environment" → Download MP4. Takes 1-3 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.

Comments

Loading comments...