Minecraft resource pack conversion
Skill AIKUSAN/minecraft-agent-skills-bundle/.agents/skills/minecraft-resource-pack-conversion
Convert or assist conversion of Minecraft Java Edition resource packs to Bedrock Edition resource packs for 1.21.x. Use for Java pack inspection, choosing Thunder or Geyser PackConverter for simple packs, JE2BE for PBR or RTX-oriented packs, running the bundled conversion helper, producing .mcpack outputs, reporting unsupported Java-only assets, and planning manual Bedrock fixes.From its SKILL.md
npx -y skills add AIKUSAN/minecraft-agent-skills-bundle --skill minecraft-resource-pack-conversionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.1 KB, 851 tokens by cl100k_base, as published. Nobody here has run it
Minecraft Resource Pack Conversion Skill
Scope
Use this skill when a Java Edition resource pack must become a Bedrock Edition
resource pack or .mcpack.
Routing Boundaries
Use when: the task is Java-to-Bedrock resource pack conversion, conversion feasibility analysis,.mcpackoutput, or unsupported asset reporting.Do not use when: the task is authoring a Java resource pack from scratch (minecraft-resource-pack), developing Bedrock add-ons (minecraft-bedrock-addon-dev), crossplay deployment (minecraft-crossplay-ops), or generating concept art (minecraft-imagegen).
Conversion Strategy
Choose a path before editing files:
| Pack shape | Preferred path |
|---|---|
| Mostly vanilla texture overrides | Built-in helper or Thunder/Geyser PackConverter |
| Pack for Geyser crossplay clients | Thunder/Geyser PackConverter, then test through Geyser |
| PBR, RTX, or physically based texture sets | JE2BE Resource Pack Converter, then manual Bedrock review |
| OptiFine CIT, custom shaders, custom models, complex sounds | Manual conversion plan with unsupported-asset report |
The bundled helper is intentionally conservative. It copies simple Java texture
assets into Bedrock-style texture folders, writes manifest.json, packages a
.mcpack, and reports everything that needs manual review.
Bundled Helper
Run from the skill folder or copy the script path from the installed skill:
python3 ./scripts/convert-java-pack-to-bedrock.py \
--input ./MyJavaPack \
--output ./MyBedrockPack.mcpack \
--pack-name "My Bedrock Pack" \
--description "Converted resource pack" \
--report ./conversion-report.json \
--converter auto
Converter modes:
auto: use a configured external converter when available, otherwise use the built-in conversion path.builtin: use only the conservative built-in converter.thunder: require a Thunder or PackConverter jar path from--thunder-jarorTHUNDER_JAR.je2be: require a JE2BE executable path from--je2be-binorJE2BE_BIN.
Use --strict when unsupported Java-only assets should fail the run instead of
producing a best-effort pack.
Built-In Conversion Behavior
The helper:
- Reads Java
pack.mcmeta. - Creates Bedrock
manifest.jsonwith unique UUIDs. - Copies
assets/<namespace>/textures/block/*.pngtotextures/blocks/. - Copies
assets/<namespace>/textures/item/*.pngtotextures/items/. - Copies common entity, GUI, environment, map, misc, painting, and particle textures into matching Bedrock folders.
- Renames a small set of known Java texture paths that differ in Bedrock.
- Copies
pack.pngtopack_icon.pngwhen present. - Writes a JSON report with copied assets, warnings, unsupported assets, and the selected converter mode.
It reports unsupported files for manual work:
- Java model JSON and blockstate JSON.
- OptiFine
optifine/assets. - Java shader overrides.
sounds.jsonand custom sound folders.- Java animation
.png.mcmetametadata. - Font and language files that need Bedrock-specific layout review.
Manual Review Checklist
After conversion:
- Import the
.mcpackinto a Bedrock client or attach it to a BDS test world. - Confirm manifest UUIDs are unique and versions match the world references.
- Inspect blocks, items, entities, UI screens, particles, and pack icon.
- Review the conversion report and resolve unsupported entries.
- If deploying to Geyser, test with a Bedrock client through the crossplay path.
Output Expectations
Return these items to the user:
- The converted pack path.
- The report path.
- A short summary of copied assets and unsupported assets.
- Any manual follow-up steps needed for Bedrock parity.
What ships with it: 1 file
11.5 KB alongside SKILL.md, 1 of them executable
scripts/
- convert-java-pack-to-bedrock.pyruns11.5 KB
Gives 0 of the 12 instructions most product growth skills give in 851 tokens
Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-07
- Read product marketing context before asking questionsin 24 of 728, across 18 files
- Define the ideal customer profilein 21 of 728, across 3 files
- Document a rollback plan before deploymentin 21 of 728, across 12 files
- Analyze the codebase to understand the productin 19 of 728, across 1 file
- Ask clarifying questions about the value propositionin 19 of 728, across 1 file
- Search for companies matching the criteriain 19 of 728, across 1 file
- Look for signals of immediate needin 19 of 728, across 1 file
- Assign a fit score from one to tenin 19 of 728, across 1 file
- Identify the target decision-maker rolein 19 of 728, across 1 file
- Suggest a personalized contact strategyin 19 of 728, across 1 file
- Provide conversation starters for outreachin 19 of 728, across 1 file
- Format results in a scannable markdown templatein 19 of 728, across 1 file
Said here and by no other author read
- choose a conversion path before editing files
- use built-in helper for simple texture overrides
- use thunder or geyser for geyser crossplay packs
- use je2be for pbr or rtx texture packs
- create manual conversion plans for complex assets
- use strict mode to fail on unsupported assets
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.