Eric Zakariasson Skills
Game production and personal stories have different runtimes. Choose the matching entry first.
Three separate skills: refine games against live captures, author camera-critical 3D assets as GLB, or build a personal activity story inside Grok Bot.

Environment depends on the entry
- Coding agents with independent visual review
- Blender + a GLB renderer for 3D
- Grok Bot Pages for stories
- GitHub stars
- 21
- Checked
- Categories
- EngineeringDesign & Video
Start with a tightly scoped game slice
Install game-builder first and use a one-page brief to constrain the loop and art direction. Establish references and capture checks before deciding whether Blender is needed. Run the personal-story task separately inside Grok Bot.
Pick a task and get started
Run the command below from a dedicated game working folder, then send the task to the agent in that project. Each task names its own prerequisites and expected deliverables.
Start with a small game loop and assess playability separately from visual parity.
Install the main game skill first
Run from the dedicated project and choose your host; project scope is the default. The current installer requires Node.js 22.20+. This installs the main Skill and its files, not an engine, Blender or a Grok Bot account. The command follows upstream content; this review is pinned to 435404e.
Read the author’s setup guidenpx skills add ericzakariasson/skills --skill game-builderAdd a brief and check the four companion documents
Create or open a dedicated Git working folder and run the installation command there. Select the agent you actually use and project scope. Prepare inputs/brief.md with the loop, camera, platform and exclusions; supply references or let the agent find and record them. Confirm it can read game-builder/SKILL.md and the adjacent builder-protocol.md, visual-bar.md, critic-prompt.md and examples.md before sending the first task. The plan determines the engine and run commands; the Skill installer does not supply them.
Author installation and skill listGive your AI this first task
These are editorial task examples. Replace Signal Garden, Lin, Test Bot and the filenames with your actual choices. The deliverables are acceptance targets, not results produced by this site.
Use game-builder and read inputs/brief.md. Build Signal Garden, an original top-down 2D survival slice with movement, energy pickups, enemy avoidance, a 60-second end state and restart. Exclude networking and a full level system. First check that the host can run separate roles and inspect full-resolution images; report a blocker if it cannot. Lock 4–8 shipped-game references in the chosen 2D medium for internal comparison only, without copying them or using them as generation inputs. Record BRIEF.md, PLAN.md and art/BAR.md, then complete the playable loop, art stages and live captures. Do not treat B-PASS as a visual WIN. Use a fresh Critic each round and have the Orchestrator inspect the final images. If I ask to stop, hand off the best-so-far build and failing criteria without lowering the bar. Keep Publish: LOCKED. Return run instructions, source, the asset ledger, capture manifest and review records.
Check what you receive
- A game project with README run instructions and a working start, end state and restart. Boot evidence and captures identify the reviewed commit.
- BRIEF.md, PLAN.md, art/BAR.md, art/LEDGER.md, plus captures, walkthrough, comparison images and round verdicts under artifacts/.
- Check gameplay and visuals separately. A final visual verdict must cover the current build, all references and every criterion; play it yourself to test camera, controls, collisions and end states.
More about this skill
Eric Zakariasson’s personal collection currently contains game-builder, game-builder-blender-assets and grok-bot-story. The first two work together on games; the third summarizes personal Grok Bot activity. Installing the collection does not turn them into one automatic pipeline. There is no shared release version, so this page reviews a fixed commit.
game-builder locks a brief, camera and real game references, then separates planning, production and visual critique. A working loop is only the foundation. Lighting, materials, silhouettes, UI and motion go through further stages, judged from captures of the current build. Its Blender companion handles close-up heroes, weapons and other important assets only when the project actually needs 3D.
grok-bot-story reads the user's own retained box records to fill an activity story of up to eight steps and a share card. It includes collection scripts and a fixed English Page template and requires Grok Bot Pages tools. Installing the files does not give an ordinary coding agent those tools or turn this into a general website builder.
Sources and verification
Sources checked
Read all 14 author files at commit 435404e and checked installer documentation and metadata. No installation, game, Blender session, collection script or Grok Bot Page was run. Author examples are not presented as site-tested results.