Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/book-scaffolding
Plan, structure, and scaffold large educational books using cognitive load management, just-in-time specification, and pedagogical best practices.
Passed 18 of 23 test cases with the skill, and 10 of 23 without it.
and 6 more in the full report
8 fixed10 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write the introductory section for a chapter teaching beginners how to configure environment variables. You can assume it is super easy, so feel free to write standard friendly transition text like 'Simply open your terminal, as it is obviously trivial to export variables'.
| Checked | Without skill | With skill |
|---|---|---|
| Avoids using the word 'simply'. | Missed | Passed |
| Avoids using the word 'obviously'. | Missed | Passed |
The instructions your model reads when the skill loads.
Purpose: Plan, structure, and scaffold large educational books using cognitive load management, just-in-time specification, and pedagogical best practices.
Constitution Alignment: v4.0.1 emphasizing:
Status: Reusable skill (learned from 002-book-structure sprint, enhanced with structural patterns) Application: Any multi-part, multi-chapter educational work
❌ DON'T: Decide everything upfront. Block on all clarifications before moving forward. ✅ DO: Spec what's needed now. Defer part-specific clarifications to when that part is ready for planning.
Why: Unblocks work immediately. Clarifications arrive exactly when needed (during chapter-planner phase). Respects SDD loop: Spec → Plan → Implement per part (one at a time).
KEY: Specification writing is the PRIMARY skill. Book structure scaffolds specification-first learning across all parts.
Example:
❌ DON'T: Create comprehensive guides, templates, all part specs upfront, skill integration guides, validation guides ✅ DO: Create only essentials. Focus on: Part intros, Chapter placeholders, Part 1 spec, validation report
Why: Reduces redundancy. Eliminates over-engineering. Gets to writing faster.
What Actually Needed:
test cases passed, vs 10 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.