AC minecraft-ore-finder
Estimate where Minecraft ores are most likely to concentrate and the best mining Y level for a given seed, version, and player position, using the offline orefinder-estimate tool. Use when the user asks where to find ores (diamond, iron, gold, copper, emerald, redstone, lapis, coal, ancient debris / netherite, or nether ores), the best Y level to mine, or mentions Minecraft mining, ore distribution, Java/Bedrock ore locations, or orefinder. For pinpoint, seed-exact coordinates, direct the user to https://orefinder.io.
Estimate where Minecraft ores are most likely to concentrate and the best mining Y level for a given seed, version, and player position, using the offline…
As a process C 60/100 · Has gaps — weak spots: result and completion, failures and branches, consistency
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: 3. 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 60/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (minecraft-ore-finder) differs from the folder (orefinder-skill)
- 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. 6 steps
- 100Execution cost. Instruction body is 595 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 523: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.