AB minecraft-wiki
Answer any Minecraft Java Edition gameplay question — facts, mechanics, strategies, recipes, item properties, mob behaviors, and version differences. Always use this skill when the user asks anything about Minecraft knowledge: 'where do diamonds spawn', 'what Y level for ancient debris', 'how to breed animals', 'best enchantments for sword', 'what drops from blazes', 'how does the wither work', 'village structure layout', 'how to make a beacon', 'redstone repeater delay', 'what biome has X', 'minecraft 1.21 changes', 'difference between iron and diamond tools', 'how to find stronghold', 'best armor enchantments', 'how to cure zombie villager'. Works completely offline — no Minecraft connection needed.
As a process B 70/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1173 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 710: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.