What problem does it solve? Systems that only their builders understand leave PMs, designers, and new hires stuck asking the same questions. This Skill turns a complex system into a multi-page, plain-English primer published as a linked Notion page tree, with machine-checked quality gates instead of manual review. ## Core Features & Use Cases - Structured course authoring: Scaffolds a primer.json config, chapter templates, and a series ordered by reader dependency, with Diátaxis explanation-style guidance and pedagogy patterns (orientation callouts, misconception callouts, check-yourself quizzes, one mermaid diagram per chapter). - Notion publishing pipeline: Converts a documented markdown subset (headings, tables, callouts, toggles, columns, mermaid diagrams) into native Notion blocks via the REST API, resolving {{slug}} cross-links and generating prev/next navigation in a two-pass publish. - Automated audit: A read-only check command verifies parenting, empty pages, leaked markdown, unresolved links, nav footers, per-chapter diagrams, hub completeness, and entry-point placement, exiting non-zero on failure. - Use Case: A team ships a design doc only engineers can read; use this Skill to produce a 10-chapter ELI5 primer with a glossary and FAQ, publish it under the design doc in Notion, and add "start here" callouts on the pages readers already visit. ## Quick Start Ask the agent to use the explainer-primer skill to create a beginner-friendly explainer course for this project and publish it to Notion under the main design doc.
