Getting-started guide, four operating-company situations, and a usage layer on the org chart

[cbrock84]

The repository had 172 skills, a live org chart, and nothing telling a newcomer how to install or use any of it.

docs/GETTING-STARTED.md (new)

Install, and then the part nobody writes: which departments to take first, chosen by what you spend your week on rather than by the org chart. Also the three ways to invoke a skill, what to expect back, how reviewer-class departments behave differently in practice, and the disclaimers explained as a category rather than left as boilerplate.

Two things it says that are worth keeping:

Install what you will use, not everything. Sixteen departments is a lot of surface, and a smaller set produces sharper triggering.

Expect to be told what the library cannot determine. A skill that names its limits is doing the job; one that answers everything confidently is the failure mode this catalog is built against.

Four operating-company situations

The seven existing situations are all shaped like a software business — SOC 2, stalled funnel, diligence. These four are shaped like a company with sites, contracts, staff and customers, supplied from real cases and scrubbed:

• A link down between two sites at 6am, with no way to prove whether it is the carrier or you
• A renewal that auto-renewed at 22% because nobody owned the notice date
• A leaver still holding shared mailbox access three weeks on
• Rate cards nobody reviewed, surfacing as a margin problem

Each names what actually comes back, not only which skills engage — which was the gap in the existing seven. And each names the uncomfortable finding, because that is the part that makes the rest credible:

• you almost certainly cannot demonstrate the demarcation point from your own monitoring, which is why the carrier call goes in circles
• the leverage was in the notice period and it is spent; the honest answer may be that you pay it this year
• discovering the access by accident three weeks later says the control that should have caught it does not exist
• it is a mix shift and an allocation basis and two accounts priced years ago — three different fixes, only one of which is a conversation with clients

Usage layer on the org chart

The live page gains a panel: marketplace add, department install, how to ask, and links to the guide, the situations and Discussions.

Two things caught by checking rather than assuming

GitHub Pages serves .md as text/markdown. The panel's links would have dropped visitors into raw text. Verified with a HEAD request and repointed at the rendered GitHub blob URLs.

The README is generated. A hand edit to it was correctly wiped by the next regenerate, so the new link went into scripts/build-readme.py where it belongs. The situation count in the README is now derived from being written once in the generator rather than in two places.

Verification

scripts/check-all.sh — all nine checks pass. Reference count is up from 247 to 271, all resolving.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01FaQP2WCqeFYH7s9pi1CJ5u

---

Generated by Claude Code