mining

Where diamonds spawn in Minecraft 1.20.

1.38x

Quality

58%

Does it follow best practices?

Impact

100%

1.38x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent-battle/skills/mining/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, well-targeted, and gives concrete executable commands for the Minecraft mining context. Its main weakness is workflow clarity: the procedure is implied through tips rather than an explicit ordered workflow with checkpoints.

Suggestions

Convert the procedure into a short numbered workflow (e.g. 1. Craft iron_pickaxe, 2. go_near to y=-55, 3. search both ore names, 4. after a vein, relocate 30+ blocks) to make the sequence and checkpoints explicit.

Trim or move the closing meta paragraph ("This skill is intentionally minimal...") since it explains the skill mechanism rather than guiding the task.

Add a brief validation/verification step (e.g. confirm iron_pickaxe is in inventory before descending) to strengthen the workflow checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Minecraft knowledge (no padding about what the game is), but the closing meta paragraph explaining what a skill does is minor over-explanation that could be trimmed, fitting the efficient-with-minor-trim anchor.	4 / 5
Actionability	It gives concrete, executable guidance such as `go_near` with `{"pos": {"x": <x>, "y": -55, "z": <z>}}`, specific ore names, and exact craft recipe, with only minor gaps (the x/z placeholders keep it from being fully copy-paste ready).	4 / 5
Workflow Clarity	A sequence is implicit (get iron pickaxe → descend via go_near → search both ore names → relocate 30+ blocks) but it is presented as tips rather than a numbered workflow with explicit checkpoints, matching the anchor with steps present but validation/sequence gaps.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed, and bold lead-ins ("To descend quickly", "relocate") give good structure, but it lacks formal section headers and includes an inline meta note, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a very specific, distinct niche but is too terse: it states the topic without describing actions and lacks any explicit "Use when" trigger guidance. Adding a trigger clause and one concrete action would lift completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when mining for diamonds in Minecraft 1.20 or when the user asks where to find diamonds or the best y-level for diamonds."

Name a concrete action in the description, e.g. "Gives diamond ore spawn y-levels, ore names, and tool requirements for efficient mining in Minecraft 1.20."

Include natural synonyms users say ("find diamonds", "diamond level", "best y for diamonds") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Where diamonds spawn in Minecraft 1.20" names a precise domain but describes no actions, matching the anchor that names the domain with minimal or generic actions.	2 / 5
Completeness	A "what" is weakly present (diamond spawn locations) but there is no "Use when..." trigger clause, so per the guideline a missing trigger caps completeness at 3.	3 / 5
Trigger Term Quality	"diamonds spawn" and "Minecraft 1.20" are natural terms a user might say, but common variations like "find diamonds", "diamond level", or "best y for diamonds" are missing, matching the anchor with some relevant keywords but missing synonyms.	3 / 5
Distinctiveness Conflict Risk	The niche (diamond spawn locations in a specific Minecraft version) is clearly distinct with only minor overlap risk against a general Minecraft skill, fitting the "mostly distinct" anchor.	4 / 5
	Total	12 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: anthropics/cwc-workshops
Path: agent-battle/skills/mining/SKILL.md
Commit: 068b84b

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.