Game Engine
v1.0.0Expert skill for building web-based game engines and games using HTML5, Canvas, WebGL, and JavaScript. Use when asked to create games, build game engines, im...
⭐ 2· 780·8 current·8 all-time
byJohn Haugabook@jhauga
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (web game engine, HTML5/Canvas/WebGL/JS) matches the provided SKILL.md, templates, and reference files. There are no unrelated requested binaries, env vars, or config paths that would be inconsistent with a game-development helper.
Instruction Scope
SKILL.md contains step-by-step tutorials, templates, and reference material limited to game-engine tasks (rendering, physics, input, publishing). It does not instruct the agent to read arbitrary system files, access unrelated environment variables, or exfiltrate data. It does mention multiplayer/WebRTC (expected for game networking) but provides guidance rather than hidden network endpoints or secret collection.
Install Mechanism
There is no install spec and no code files that would be downloaded or executed by the platform; this instruction-only format minimizes install-time risk.
Credentials
The skill requests no environment variables, credentials, or config paths. That is proportional to a documentation/templates skill. (Note: implementing multiplayer or publishing in real projects will require external credentials/servers, but that is outside this skill's declared scope.)
Persistence & Privilege
The skill is not forced-always, and allows normal autonomous invocation by the agent (platform default). It does not request persistent system modifications or elevated privileges.
Assessment
This skill appears coherent and low-risk because it's instruction-only documentation and templates for web game development. Before using the templates in production: (1) review any third-party license terms (Phaser, Three.js, GameBase, etc.); (2) inspect any copied code for unsafe patterns (eval, remote script loading, or hard-coded endpoints) before running it in your environment; (3) if you implement multiplayer (WebRTC/WebSockets), plan for STUN/TURN servers and secure signaling—those require network infrastructure and credentials outside this skill; (4) be aware that mobile features (Device Orientation, vibration, audio autoplay) trigger browser permission/UX considerations; and (5) always test new code in a sandboxed/dev environment before deploying.Like a lobster shell, security has layers — review code before you run it.
latestvk97427erqfgqx37rtpa1vc9cmx81pcbh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.