Guild Lore: The Grand Library

guild-lore is not a Weapon that does work. It is a reference index over every other Weapon in this package, distilled one guide per corpus pillar. Its purpose is to get an orchestrator or sub-agent oriented fast: which Weapons exist for a domain, who owns what when two Weapons look similar, what sequences chain them together, and what hard rules and gotchas are load-bearing enough to know before touching that domain at all.

The double-reinforcement contract

Every pillar guide below is loaded through two independent reinforcement points, by design:

1. The index line below names the guide's Weapons in a MANDATORY LOAD: list, right next to the link. An orchestrator reading only this SKILL.md already knows what to load before opening the guide.
2. The guide itself repeats the same Weapon list at the very top, under a CRITICAL DIRECTIVES header, with a one-line why-each.

This is deliberate redundancy, not an oversight. An agent that skims only the index still gets the load list. An agent that jumps straight to a guide (via a direct file reference, a search hit, or a sub-agent hand-off that skipped SKILL.md) still gets the load list from the guide's own header. Two independent surfaces stating the same mandatory loads means the instruction survives being encountered from either direction, and the act of loading each named Weapon is itself how the orchestrator's context absorbs the Guild's arsenal rather than just pointing at it.

Load guild-lore itself first to get the map. Then load the specific pillar guide for the domain in play. Then load every Weapon that guide's CRITICAL DIRECTIVES block names, via the Skill tool, before acting.

How to use this skill