mining

$npx mdskill add anthropics/cwc-workshops/mining

Locate diamond ore coordinates in Minecraft 1.20+ for efficient mining.

  • Identifies deepslate_diamond_ore positions below y=0 in the game.
  • Requires iron_pickaxe crafting before attempting any ore extraction.
  • Uses go_near to descend rapidly without wasting durability.
  • Suggests relocating 30+ blocks horizontally after exhausting a vein.

SKILL.md

.github/skills/miningView on GitHub ↗
---
name: mining
description: Where diamonds spawn in Minecraft 1.20.
---

Diamond ore generation peaks at **y ≈ -58** in Minecraft 1.18+. The
pre-1.18 advice of y=11 is obsolete.

Below y=0, the ore is almost always `deepslate_diamond_ore`, not
`diamond_ore` — search for both names.

An **iron_pickaxe is required** — diamond ore mined with a
stone_pickaxe or weaker drops nothing. Craft the iron_pickaxe (3
iron_ingot + 2 sticks at a placed crafting_table) before mining
diamond. A diamond_pickaxe is not required.

**To descend quickly**, call `go_near` with your current x/z and a
deep y (e.g. `{"pos": {"x": <x>, "y": -55, "z": <z>}}`) — the
pathfinder digs straight down in one action. Don't `mine_block`
stone repeatedly to descend; it wastes turns and pickaxe durability.

After exhausting a vein, **relocate** — `go_near` to a position 30+
blocks away horizontally at the same y before searching again.
Diamond veins do not cluster; tunneling the same corridor repeatedly
wastes turns.

(This skill is intentionally minimal. It's an example of what
attaching a skill does — it puts these facts in the agent's context.
Edit this file to add more, or write strategy directly in your
AGENT['system'] prompt.)

More from anthropics/cwc-workshops

SkillDescription
edgartools-sec-dataHow to pull SEC EDGAR data with the edgartools Python package — company lookup, filings, XBRL financial statements, and filing sections like Item 1A risk factors. Use whenever a task involves SEC filings, 10-K/10-Q data, or company financials.
forecastingHow to produce a demand forecast for a SKU, and when to delegate that to a subagent vs. compute it yourself. Load this for any task involving "forecast", "how much will we sell", "next month", promos, or seasonal SKUs.
incident-triage-runbookThe SRE team's runbook for triaging production latency and error-rate incidents. Use this whenever investigating an incident, a latency spike, elevated error rates, or when asked "what caused X" about a production service.
notify-templatesFixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
postmortem-reportHow the SRE team writes a postmortem PDF. Use this whenever asked for a postmortem, an incident report, a write-up to share, or a PDF of what happened.
reorder-policyHow to decide whether and how much to reorder a SKU. Load this whenever a task involves reorder recommendations, purchase orders, or "should we restock" questions.
submit-solutionGuide a workshop attendee through committing their starter-agent decomposition and opening a PR with their solution + workshop feedback. Invoke when the user says "submit", "I'm done", "open a PR", or asks how to share their solution.
supplier-selectionHow to rank and pick a supplier for a SKU. Load this whenever a task involves choosing a supplier, comparing quotes, or creating a purchase order.
weekly-reportStructure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".
workshopWorkshop coach for the Research Desk (SEC agents) workshop. Use when the user types /workshop, asks for a workshop act or module ("act 2", "next act", "where am I"), wants a TODO(workshop-N) implemented or explained, or asks for help following WORKSHOP.md.