Game Compare Backends

v1.0.0

Run a narrow compare between two or three backend profiles when architecture uncertainty is real. Use carefully, because it usually costs more tokens and time.

0· 117·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 mike007jd/game-compare-backends.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Game Compare Backends" (mike007jd/game-compare-backends) from ClawHub.
Skill page: https://clawhub.ai/mike007jd/game-compare-backends
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
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 game-compare-backends

ClawHub CLI

Package manager switcher

npx clawhub@latest install game-compare-backends
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the runtime instructions: a narrow compare of two or three backend profiles. The bundle requests no credentials, binaries, or installs that would be unrelated to that purpose.
Instruction Scope
SKILL.md asks the agent to produce/update docs/game-studio/backend-decision.md and notes that best results come with file read/write access and ability to build/test prototypes. This is coherent for an architecture comparison, but it implies the agent may read and modify project files and run builds/tests — you should confirm and control those permissions before use.
Install Mechanism
No install spec and no code files to execute. Instruction-only skills have the lowest install risk because nothing is pulled or written to disk by an installer.
Credentials
The skill declares no required environment variables, credentials, or config paths — consistent with a documentation/analysis helper. It does mention filesystem access in compatibility metadata but does not request secrets or external service tokens.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent presence or modifications to other skills or system-wide settings.
Assessment
This skill appears coherent and low-risk, but review these before installing: (1) The skill expects to read/write project files (it targets docs/game-studio/backend-decision.md). Only grant file-system or repo write access in a workspace you trust, and require explicit confirmation before it modifies files. (2) The skill may recommend running builds or tests for best results — avoid giving it permission to run destructive commands and consider running any suggested builds/tests yourself in a sandbox. (3) Because it can modify documentation, require a human review/commit step (or use a branch/pull request) so you can inspect changes before they land. If the skill later requests network endpoints, credentials, or an installer, re-evaluate immediately — that would be a red flag.

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

latestvk97ajh75ggr5yvy6frb4gv900n83xzhh
117downloads
0stars
1versions
Updated 4w ago
v1.0.0
MIT-0

Game Compare Backends

Goal

Help choose between backend profiles when the choice is genuinely uncertain.

Important warning

Compare mode usually costs more tokens and time than a single recommended route. Say this explicitly before or while using it.

Good use cases

  • greenfield work where two routes appear plausibly viable
  • UI-first vs world-first uncertainty
  • 2D vs lightweight 3D preview uncertainty

Bad use cases

  • obvious stack choice
  • live-product iteration
  • post-architecture situations where the real blocker is not the backend

Deliverable

Update docs/game-studio/backend-decision.md with:

  • compared options
  • criteria
  • result
  • why the winner won
  • token / cost note

Comments

Loading comments...