module-binder

Compile adventure directories into a single module.md with inline references and SRD rules.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/giodl73-repo/QUEST --skill module-binder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: module-binder
Source: https://github.com/giodl73-repo/QUEST/tree/main/.claude/skills/module-binder
Command: npx skills add https://github.com/giodl73-repo/QUEST --skill module-binder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compile the contents of an adventure directory into a single module.md that a DM can open at the table and run cold.

Core Features & Use Cases

  • Inline references: resolve and inline cross-file content to produce a cohesive module.
  • SRD inlining: embed essential SRD rules directly in the DM Cheatsheet for quick reference.
  • Output structure: generate adventures/<slug>/module.md with a complete set of rooms, encounters, treasures, and NPCs.

Quick Start

Run the module-binder on an adventure directory to produce adventures/<slug>/module.md.

Frequently Asked Questions about module-binder

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

FAQPage Schema
How do I compile a D&D adventure directory into a single markdown file for DM use?

To compile a D&D adventure into a single markdown file, run the module-binder on your adventure directory to process rooms, encounters, and NPCs into a cohesive module. It outputs a DM-ready module.md with inlined content.

Can I inline cross-file references and SRD rules into a printable adventure module?

Yes, you can inline cross-file references and SRD rules into a printable adventure module. The compiler resolves cross-file content and embeds essential SRD rules directly into a DM Cheatsheet for quick reference.

How does adventure compilation handle stat blocks and cross-references?

Adventure compilation handles stat blocks and cross-references by validating links between files and inlining content directly into the output. This ensures the final module.md contains complete, inline stat blocks without broken references.

What do I need to generate a DM-ready module from scattered markdown adventure files?

To generate a DM-ready module from scattered markdown adventure files, you need an adventure directory containing your premise, rooms, encounters, treasures, and NPCs. The binder processes these to output adventures/<slug>/module.md.

Are there limitations to compiling an adventure module with inline references?

A limitation of compiling an adventure module with inline references is that the tool expects a structured adventure directory format to function properly. It specifically outputs a module.md file and requires correctly formatted input files to validate cross-references successfully.