← ClaudeAtlas

skill-build-educational-sitelisted

Build a single self-contained HTML explainer page on a technical or regulatory topic. ALWAYS trigger when the user wants a deliverable webpage that explains something — phrasings include "one-pager", "primer", "explainer", "teaching page", "deep-dive page", "self-contained webpage", "single HTML file on X", "page on Y to execs and engineers". Trigger even without "educational site" — "presenting Thursday on X, build me an HTML page", "deep-dive page on Y", "brief my team, make an html page on Z" all qualify. Strong on regulated/security topics (FAPI, PCI-DSS, DORA, SPIFFE, CALM, FIPS, SLSA, SBOM, AI Act, OAuth, zero-trust) but works for any technical concept. Skip ONLY for different artifacts (slide deck, Confluence, README, ADR, dashboard, multi-page docs site) or chat-only answers.
jamesbuckett/skill-build-educational-site · ★ 0 · Web & Frontend · score 72
Install: claude install-skill jamesbuckett/skill-build-educational-site
# skill-build-educational-site ## What this produces One file: a self-contained `.html` document, no build step. Opens in any browser. Looks professional enough to share with a regulator, an executive sponsor, or a new joiner — same artifact, different reader. External dependencies are minimised: Mermaid via CDN is the default when a page needs diagrams it would be painful to hand-author (sequence diagrams, C4 containers, large flowcharts), but **inline-SVG diagrams are a first-class alternative** and the right choice when the page needs to be strictly self-contained (corporate environments without CDN egress, archival use, true "send one file" portability). Choose per page, not per skill. The page is **single-topic and dense**. Not a course, not a multi-page site. One concept, layered so it works for three audiences in the same file: - **Executives** — want the TL;DR, the diagram, the regulatory implication, the trade-off table - **Practitioners** — want the protocol detail, the config snippet, the failure modes - **General learners** — want the analogy, the glossary, the "why does this matter" A runtime audience switcher (a control in the header) toggles visibility of practitioner-depth blocks so the same file serves all three readers without forcing anyone to scroll past content that isn't for them. ## When to use Use this skill any time the user wants explanatory content rendered as a deliverable page rather than a chat reply. Triggers include the obvious ("build