sya-ri/minecraft-skills/minecraft-datapacks

Minecraft Datapacks

Use this skill for Java Edition data pack work. Resolve the target version before giving version-specific facts.

Workflow

1. If the user gives no version, assume the latest bundled Java release and state that assumption.
2. Read references/versioning.md before making compatibility claims.
3. Use the minecraft-skills CLI for machine-verifiable facts. If the CLI is not available, use

the bundled references in this skill and clearly state when strict data is not bundled.

1. Before task-wording searches, translate non-English user intent into concise English canonical

Minecraft terms. Use the English terms only for lookups, and keep the user's requested response language. Keep exact identifiers, namespace IDs, file paths, and content literals unchanged. Then use minecraft-skills datapack search "<task>" before broad list commands when you need to find relevant recipes, intents, guardrails, diagnostics, claim policies, fact surfaces, source tiers, datasets, or version-support entries.

1. Use minecraft-skills datapack intents to choose the exact lookup path for the user's intent.
2. Use minecraft-skills datapack recipes to choose an ordered workflow for common tasks such as

function commands, observed JSON, and migrations.

1. Use minecraft-skills datapack search-scenarios "<task>" to route user wording to an existing

scenario without inventing one.

1. Use minecraft-skills datapack scenarios when you need all realistic evaluation cases for the

domain.

1. After choosing a scenario, use minecraft-skills datapack plan <scenario-id> <version> to

resolve the exact recipes, intent lookups, diagnostics, claim policies, fact surfaces, response patterns, and evidence required for that task.

1. Use minecraft-skills datapack context <version> when you need preflight, intent routing, and

evidence in one payload.

1. Use minecraft-skills datapack guardrails and minecraft-skills datapack diagnostics before

finalizing generated files or commands.

1. Use minecraft-skills datapack claim-policies before making version, command, JSON shape, or

path claims.

1. Use minecraft-skills datapack output-requirements and

minecraft-skills datapack response-patterns before finalizing an answer or generated files.

1. Use minecraft-skills datapack fact-surfaces to check what each data surface can and cannot

prove.

1. Use minecraft-skills datapack preflight <version> before generating files or commands.
2. Use minecraft-skills minecraft support-matrix to check which version-specific facts are

bundled and which heavyweight facts are downloadable.

1. Use minecraft-skills minecraft support --domain datapack when choosing among target versions.
2. Use minecraft-skills datapack evidence <version> when explaining which sources and extracted

files back an answer.

1. If an observed datapack schema surface is needed but not available locally, inspect

minecraft-skills data manifest, then fetch the matching datapack-schema-surface entry before relying on it.

1. For migrations between versions, inspect compare-commands and compare-vanilla-paths before

describing command or vanilla data additions/removals.

1. Use minecraft-skills datapack schema <version> and

minecraft-skills datapack search-schema <version> for observed vanilla datapack JSON field shapes. Treat this as observed vanilla data, not a normative schema.

1. Treat null, unknown, seed, and not-extracted fields as gaps. Do not convert them into

facts.

1. Do not fetch, crawl, summarize, or cite Minecraft Wiki pages in AI workflows. Use bundled data,

Mojang-derived data, source reports, and allowed structured community datasets instead.

CLI Commands

• minecraft-skills minecraft show <version>, minecraft-skills minecraft pack-formats,

minecraft-skills datapack preflight <version>, minecraft-skills datapack context <version>, minecraft-skills datapack search "<task>", minecraft-skills datapack recipes, minecraft-skills datapack recipe <id>, minecraft-skills datapack search-scenarios "<task>", minecraft-skills datapack scenarios, minecraft-skills datapack scenario <id>, minecraft-skills datapack plan <scenario-id> <version>, minecraft-skills datapack guardrails, minecraft-skills datapack diagnostics, minecraft-skills datapack diagnostic <id>, minecraft-skills datapack claim-policies, minecraft-skills datapack output-requirements, minecraft-skills datapack response-patterns, minecraft-skills datapack response-pattern <id>, minecraft-skills datapack evidence <version>, minecraft-skills source report datapack <version>, minecraft-skills datapack intents, minecraft-skills datapack intent <id>, minecraft-skills datapack checklist, minecraft-skills minecraft support --domain datapack, minecraft-skills datapack fact-surfaces, minecraft-skills minecraft support-matrix, minecraft-skills data manifest, minecraft-skills data fetch datapack-schema-surface --version <version>, minecraft-skills minecraft compare <from> <to>, minecraft-skills datapack server-reports <version>, minecraft-skills datapack schema <version>, minecraft-skills datapack search-schema <version>, minecraft-skills datapack compare-schema <from> <to>, minecraft-skills datapack commands <version>, minecraft-skills datapack compare-commands <from> <to>, minecraft-skills datapack vanilla-paths <version>, minecraft-skills datapack compare-vanilla-paths <from> <to>, minecraft-skills minecraft vanilla-inventory <version>

Source Priority

Use official Mojang version metadata and extracted vanilla game data for facts. Use minecraft-skills source report to confirm allowed source tiers. Treat Minecraft Wiki as human-only background and do not fetch, crawl, summarize, or cite it in AI workflows.