Inspect game state
Community Agent Skills for OpenAllay
npx -y skills add nkanf-dev/OpenAllay-Skills --skill inspect-game-stateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 12 days oldThe repository was created 12 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when troubleshooting requires correlating two or more Minecraft client, settings, HUD, or F3 areas.
SKILL.md
2.2 KB, as published. Nobody here has run it
Use this Skill for multi-step diagnosis or correlation across Minecraft menus,
the player's own UI, HUD/F3, installed-content screens, and closed
non-mutating queries. Do not load it for an obvious direct lookup such as
“list my installed mods” or “what biome am I in”; query mc.game directly.
Select and correlate only the required sections:
mc.game.runtime: version, loader, topology, and runtime identity.mc.game.mods.installed: installed mod metadata. This direct exact-path lookup does not require schema probing.mc.game.options.values: option values and key mappings across video, sound, controls, mouse, accessibility, language/chat, online/privacy, packs, and general settings.mc.game.packs: selected and available resource/data packs.mc.game.shaders: shader state and options. Treat an unavailable integration as unavailable; do not infer shader state from installed files.mc.game.diagnostics: section metadata; its.valuesarray contains detached F3-style position, direction, dimension, biome, renderer, performance, target, and network values.mc.game.playerandmc.player: only the caller's visible state.mc.game.worldQueries: time, weather, difficulty, world border, and spawn.
Biome, coordinates, dimension, direction, yaw, and pitch come from diagnostics and never require server command permission. Return a compact correlation and retain authority/completeness metadata. If a section is partial or unavailable, say what is unavailable and stop rather than guessing.
Recipes and Guides are separate deep-content domains; load their Skills for
those questions. Spatial block/entity observation is also outside this
troubleshooting Skill: use the core top-level world binding directly with
roots: ["world"] when that request capability is available. Maps, structures,
another container's contents, arbitrary paths/classes, raw commands, and every
write or world interaction remain outside this Skill.