Video Game Maker Free 3d

Turn a set of character sprites and background images into 1080p 3D game videos just by typing what you need. Whether it's creating 3D game trailers and game...

Security Scan

The skill's declared token and API usage align with its stated cloud-rendering purpose; no installs or unrelated credentials are requested, but there are small inconsistencies and privacy implications you should understand before using it.

Purpose & Capability

The skill is an instruction-only connector to a cloud rendering API. Requesting a single service token (NEMO_TOKEN) and making HTTP calls to a rendering API is coherent with creating 3D videos on cloud GPUs.

Instruction Scope

SKILL.md instructs the agent to obtain/use NEMO_TOKEN (use env var or request an anonymous token), create sessions, upload user-supplied files, stream SSE, and poll render status. These actions are within the stated purpose, but the instructions also require: reading the skill's YAML frontmatter at runtime to set attribution headers and detecting the agent install path (filesystem checks like ~/.clawhub or ~/.cursor/skills/) — both expand the agent's scope beyond pure network calls and should be noted.

Install Mechanism

No install spec or code files — instruction-only. This is lowest-risk for on-disk execution since nothing is downloaded or installed by the skill itself.

Credentials

The single required env var (NEMO_TOKEN) is appropriate for a cloud API. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) not declared in the registry metadata — an inconsistency. Also some attribution headers mentioned in the doc are not fully enumerated in the truncated text; confirm which headers/values are required. The skill will accept and upload user media to the external API, so the token and any uploaded content are sensitive.

Persistence & Privilege

always is false and there is no install-time persistence. The skill asks to save a session_id from the API (expected for session workflows) but does not request system-wide privileges or modifications to other skills.

Scan Findings in Context

[no_regex_findings] expected: The static regex scanner found nothing — expected because this is an instruction-only skill with no code files to analyze.

Assessment

This skill connects to an external service (mega-api-prod.nemovideo.ai) and will upload any images/video you provide and use a NEMO_TOKEN to authenticate. Before installing: 1) Confirm you trust the external domain and its privacy policy — uploaded media will leave your device. 2) Be aware the skill may check ~/.config and detect install paths to set attribution headers (registry metadata and SKILL.md disagree about config paths). 3) If you don't have a persistent NEMO_TOKEN, the agent will request an anonymous token for you; treat that token as sensitive. 4) Avoid uploading sensitive or private images to this skill. 5) If you want more assurance, ask the skill author for a homepage or owner contact and for clarification of the exact headers it will send (the SKILL.md references additional attribution headers that are not fully shown).

Getting Started

Share your images, video clips and I'll get started on 3D game video creation. Or just tell me what you're thinking.

Try saying:

• "create my images, video clips"
• "export 1080p MP4"
• "create a 3D game trailer video"

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 3D — Create 3D Game Videos Free

Drop your images, video clips in the chat and tell me what you need. I'll handle the 3D game video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a set of character sprites and background images, ask for create a 3D game trailer video with animated scenes and transitions, 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 — use simple looping animations as input to get smoother 3D scene output.

Matching Input to Actions

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

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

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

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

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "create a 3D game trailer video with animated scenes 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 3D game trailer video with animated scenes and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across game platforms and social media.