What problem does it solve? Most developer tutorials fail silently: readers abandon at a broken step, copy-paste their way to a working app without learning anything, or discover a hidden prerequisite halfway through. This Skill turns tutorial writing into a disciplined process so the page actually transfers a skill instead of demoing the product. ## Core Features & Use Cases - Greenfield tutorial authoring: Runs a structured interview, applies backward design (objective first, then evidence, then steps), builds a concept ladder with a chosen stop rung, and drafts the page against a section-by-section outline template. - Tutorial audits: Requires cold runs by level-matched learners, then returns a step-keyed defect table classifying each issue as defect, hidden prerequisite, concept gap, or friction, ordered by learners blocked. - Scope calls and measurement: Distinguishes tutorials from how-to guides and quickstarts using Diátaxis, and defines Kirkpatrick-sorted KPIs including transfer tests, per-checkpoint drop-off, and downstream product behavior. - Use Case: A docs lead says "nobody finishes our webhooks tutorial." The Skill prescribes cold-run verification, identifies that step 4 introduces three concepts at once, and returns a prioritized fix table rather than a prose critique. ## Quick Start Ask the assistant to write a tutorial teaching developers to stream responses from your SDK, or to audit an existing tutorial that learners abandon.
