Video Game Maker Free

Turn a set of character sprites and background images into 1080p game video trailer just by typing what you need. Whether it's creating game trailers or demo...

Security Scan

The skill's requests and runtime instructions are consistent with its stated purpose (remote video rendering) and only require a single service token; there are no surprising credentials or install steps — but it will upload your assets to an external API you should trust.

Purpose & Capability

Name/description (create game videos from assets) match the runtime instructions: all API endpoints, upload, SSE-based editing, session and export flows target a remote rendering service. The single required env var (NEMO_TOKEN) is appropriate for authenticating to that service.

Instruction Scope

Instructions direct the agent to create or reuse a NEMO_TOKEN, open a session, upload user-provided assets, stream SSE messages, and poll for render status — all inline with a cloud-render workflow. The SKILL.md also instructs the agent to read the skill's YAML frontmatter and detect install path to populate attribution headers; this means the agent will read its own skill file and may inspect its install location. There are no instructions to read unrelated system files or other environment variables. Users should understand that their image/audio assets and session metadata will be transmitted to the external API host (mega-api-prod.nemovideo.ai).

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is downloaded or written by the skill itself. That minimizes installation risk.

Credentials

Only NEMO_TOKEN is required and declared as the primary credential. That is proportionate for a service that requires authenticated uploads and exports. The skill also supports generating an anonymous token via the service's anonymous-token endpoint if no token is provided (100 credits, 7-day expiry).

Persistence & Privilege

The skill does not request always:true and does not modify other skills or system-wide settings. It will create session state on the remote service (session_id, render jobs) but does not demand elevated platform privileges.

Assessment

This skill appears to do what it says: it uploads your images/audio to a remote rendering API (mega-api-prod.nemovideo.ai) and returns a rendered video. Before installing: (1) confirm you trust the external service and domain — your assets and metadata will be transmitted and stored there; (2) understand NEMO_TOKEN is a Bearer credential giving access to your account on that service (use a limited-scope or anonymous token if possible); (3) the skill will read its own SKILL.md and detect its install path to set attribution headers — benign but note it inspects its runtime environment; (4) avoid uploading sensitive PII or proprietary assets unless you accept external hosting. If you need stronger guarantees, request the vendor’s privacy/security docs or run the skill in a sandboxed environment.

Getting Started

Ready when you are. Drop your images, audio, assets here or describe what you want to make.

Try saying:

• "create a set of character sprites and background images into a 1080p MP4"
• "turn my game assets into a playable-looking trailer with sound effects and transitions"
• "creating game trailers or demo videos from game assets for indie game developers"

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.

Video Game Maker Free — Create Game Videos From Assets

Send me your images, audio, assets and describe the result you want. The AI game video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a set of character sprites and background images, type "turn my game assets into a playable-looking trailer with sound effects and transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: using consistent pixel art or themed assets gives the output a more polished game-like feel.

Matching Input to Actions

User prompts referencing video game maker free, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-game-maker-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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

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)

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 "turn my game assets into a playable-looking trailer with sound effects and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across itch.io, Steam, and social platforms.

Common Workflows

Quick edit: Upload → "turn my game assets into a playable-looking trailer with sound effects and transitions" → 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.