mcmod-environment-reporter

Extract Minecraft mod metadata and side requirements into Markdown reports.

Updated May 16, 2026
One-click install
npx skills add https://github.com/qwaecd/mcmod-environment-reporter --skill mcmod-environment-reporter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcmod-environment-reporter
Source: https://github.com/qwaecd/mcmod-environment-reporter/tree/main
Command: npx skills add https://github.com/qwaecd/mcmod-environment-reporter --skill mcmod-environment-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Producing accurate client/server install-side support documentation for Minecraft mods is tedious and error-prone when it requires manual inspection of each mod jar, often leading to uncertainty or guesswork.

Core Features & Use Cases

  • Jar metadata-driven reporting: Inspects Minecraft mod .jar files and extracts real mod name/id and loader/platform plus version and metadata source.
  • Client/Server side summarization: Produces separate client_side and server_side fields so you can audit mod compatibility by side.
  • Optional structured online verification: After offline review, optionally validates uncertain entries using Modrinth structured hash matching and (opt-in) lower-confidence project search fallback.
  • Optional jar classification workflow: After a report exists and with explicit user request, copies or moves jars into classification directories based on report rules or exported selections.

Quick Start

Use the skill to analyze the mods in ./mods and write a Markdown report to mod-environment-report.md.

Frequently Asked Questions about mcmod-environment-reporter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a client and server side support report for Minecraft mod jars?

To generate a client and server side support report for Minecraft mod jars, this Skill scans a directory of .jar files to extract metadata names, mod IDs, versions, and platform requirements into a Markdown report. It performs a non-recursive scan directly inside the provided directory.

What is the best way to audit modpack compatibility for client and server side requirements?

The best way to audit modpack compatibility for client and server side requirements is by scanning .jar files to extract metadata and summarize side support. This produces separate client_side and server_side fields so you can verify install requirements per mod.

Can I verify Minecraft mod metadata against Modrinth using jar hash matching?

Yes, you can verify Minecraft mod metadata against Modrinth using exact jar hash matching. After offline review, the Skill optionally validates uncertain entries with structured online verification and an opt-in lower-confidence project search fallback.

Does jar scanning support recursive subdirectory searches for Minecraft mods?

No, jar scanning does not support recursive subdirectory searches for Minecraft mods. The Skill requires a non-recursive scan of .jar files located directly inside the provided directory to ensure accurate metadata extraction.

How do I classify Minecraft mod jars based on their client or server side support?

To classify Minecraft mod jars based on their side support, you can use the optional jar classification workflow. After a report exists and with explicit request, the Skill copies or moves jars into classification directories based on report rules or exported selections.