Skills — Library
A skill is a folder at .claude/skills/<name>/ containing a SKILL.md. The description loads eagerly so Claude knows the skill exists; the body only loads when the skill is invoked. The primer on what skills are and when to author one is in Skills (Foundations) — this page is the library: an index of every skill the Playbook touches, with one row per skill telling you where the canonical content lives and which other pages reference it.
The library exists because skills get named from prompts, templates, CLAUDE.md files, and walk-throughs across the Playbook, and chasing them down by grepping was getting tedious. Adding a skill anywhere in the Playbook means adding it here too — that’s the index discipline.
Propagation rule
Section titled “Propagation rule”A skill’s name and description appear in more than one place: the skill’s own SKILL.md, this library page, every Playbook section that names it, and any CLAUDE.md that references it. When any of those changes, search the others and update them in lock-step. The Referenced in column on each row of the tables below is the search list for that skill — start there.
The same rule runs the other way: when a new skill enters the Playbook from any section, add a row here with its referenced-in list populated. The library is the closest thing to a propagation manifest.
Authored skills
Section titled “Authored skills”Skills written for the Playbook, with the full SKILL.md reproduced in a code fence on the detail page so you can copy-paste it into your own .claude/skills/ folder.
| Skill | When to reach for it | Referenced in |
|---|---|---|
pptx-from-brain-dump | Generate a .pptx deck from a brain-dump and a branded PPTX template. Last stage of the brain-dump → layout → pptx pipeline. | Output Routes Overview |
Documentation pending
Section titled “Documentation pending”Skills referenced in Playbook sections but without a SKILL.md yet captured in the library. Tracked as backlog work. Until each lands a detail page here, treat the referencing sections as the authoritative descriptions.
| Skill | What it does (per referencing sections) | Referenced in |
|---|---|---|
brain-dump-cleaner | Cleans up raw brain-dumps — typos, contradictions, duplicate ideas — so downstream pipelines work from a clean source. First stage of the brain-dump → layout → pptx and brain-dump → layout → HTML pipelines. | Output Routes Overview, Presentation Bootstrap, Flexible HTML template, pptx-from-brain-dump |
content-to-layout | Maps a cleaned brain-dump into a layout map — one line per slide or section, each tagged with a layout name from a fixed vocabulary (title, prose, bullets, stat, two-column, option-cards, canvas). The contract between content and rendering. | Output Routes Overview, Presentation Bootstrap, Flexible HTML template, pptx-from-brain-dump |
layout-designer | Designs bespoke layouts when the seven defaults can’t capture the content shape — decision trees, scrolling comparisons, novel interactions. Opt-in; only invoked before the flexible HTML template when the content needs it. | Output Routes Overview, Flexible HTML template |
Upstream skills
Section titled “Upstream skills”Skills from Anthropic’s skills repo. Not authored here, not reproduced in this library — install them at user level following the Command Centre setup instructions.
| Skill | What it does | Referenced in |
|---|---|---|
xlsx | Excel file generation and manipulation. Installed at ~/.claude/skills/xlsx/. | Command Centre setup, Config resolution |
pptx | PowerPoint generation from source content. Built-in primitives used by pptx-from-brain-dump. Installed at ~/.claude/skills/pptx/. | Output Routes Overview, Command Centre setup, Config resolution, Presentation Bootstrap, pptx-from-brain-dump |
Internal — Playbook editing only
Section titled “Internal — Playbook editing only”The Playbook dogfoods itself with its own skill. Not intended for use in other projects.
| Skill | What it does | Lives at |
|---|---|---|
content-architecture | Encodes the rules for editing Playbook content — IA groups, numbering, frontmatter, voice. Loaded whenever Claude edits content in src/content/docs/. | .claude/skills/content-architecture/SKILL.md |
How a skill page is laid out
Section titled “How a skill page is laid out”Each authored skill page has the same shape: a short Playbook-side intro explaining when the skill fits and what it depends on, followed by the full SKILL.md body inside a code fence. Copy the fenced block straight into .claude/skills/<skill-name>/SKILL.md — no edits needed.
If a skill references other skills, the intro paragraph names them and links to their pages or rows above. If it references a Playbook template or HTML artefact, the intro links to that too. The body inside the fence is verbatim — don’t edit cross-references inside the fence to point at Playbook URLs, because the fence is the file you’d paste into your own .claude/skills/ folder.