What problem does it solve? Installing Minecraft mod loaders requires querying four different metadata APIs, downloading installer jars, and running Forge/NeoForge processors headlessly, all with subtle per-loader quirks that are easy to get wrong. ## Core Features & Use Cases - Version Discovery: Lists available loader versions for Fabric, Quilt, Forge, and NeoForge through their respective metadata endpoints, including NeoForge's version-to-Minecraft mapping rules. - Headless Installation: Installs loader versions into cache/versions/ and cache/libraries/ with inheritsFrom version JSON, running Forge/NeoForge installer processors via a pluggable ProcessRunner test seam. - Cache Short-Circuiting: Skips all network and processor work when a repeated install finds a complete cache, using sha1 sidecar files to tolerate zlib-ng recompression differences. - Use Case: When adding NeoForge support to gcl-core, consult this Skill to learn that Minecraft 1.20.1 has no neoforge artifact and that 1.20.2 must be used for verification instead. ## Quick Start Read this Skill before modifying anything under gcl-core loaders/ so the loader install code follows the documented API endpoints and processor algorithm.