Skill: Creating Workbooks
A workbook is a step-by-step guide that takes someone from zero to agentic workflow using Claude Code.
When to Use This Skill
Use this when someone needs to learn a repeatable task using Claude Code, and you want them to:
- •Build the habit through daily use
- •Reach an agentic mindset (not just tool proficiency)
- •Have clear checkpoints so they don't get stuck
Workbook Structure
Every workbook follows this arc:
| Phase | Steps | Purpose |
|---|---|---|
| Setup | 1-2 | Environment ready, materials gathered |
| Foundation | 2-3 | Teach Claude the context, capture learner's voice/style |
| Concept | 1 | Brief explanation of key concept (skills, delegation, etc.) |
| Build | 2-4 | Create incrementally, test, refine |
| Expand | 1-2 | Apply pattern to more cases |
| Ongoing | 1 | No gate - continuous improvement |
Total: 8-12 steps. Fewer feels rushed, more feels overwhelming.
Writing Gates
Every step except the final one needs a gate - how the learner knows they're ready to proceed.
Gate Principles
- •Self-verifiable - They don't need someone else to check
- •Concrete - Not "you understand X" but "you can do Y"
- •Quick to test - Under 30 seconds to verify
Gate Patterns
| Type | Example |
|---|---|
| Ask Claude | "Ask Claude 'what types of reports do I review?' - it answers correctly" |
| Run command | "Run python review.py report.md and it produces output" |
| Inspect output | "Read the generated comments and think 'I'd say something like this'" |
| Explain back | "You can explain in one sentence what a skill does" |
| File exists | "The skills/ folder has 3 skill directories" |
Bad Gates (Avoid)
- •"You feel comfortable with..." (not verifiable)
- •"You understand..." (too vague)
- •"Claude works correctly" (what does 'correctly' mean?)
Writing Sample Prompts
Sample prompts are starting points, not solutions.
Principles
- •Deliberately imperfect - Good enough to work, rough enough to improve
- •Explain intent - What outcome they want, not just what to do
- •Leave room - Don't over-specify so learner can make it theirs
Example
code
Read all the files in reports-for-review/. I need you to understand the different kinds of reports I review. These are security assessment reports that our consultants write, and I review them before they go to clients. After reading them, tell me: - What types of reports these are - What sections they typically have - What kind of issues/findings they contain Then create a claude.md file that captures this understanding.
This prompt works but isn't optimal. The learner will naturally refine it.
Identifying Learner Resistance
Before writing a workbook, understand what might hold the learner back.
| Resistance | How to Address |
|---|---|
| "I can do it faster myself" | Show the compound benefit over time |
| "I don't trust the output" | Build in explicit review checkpoints |
| "This is too abstract" | Ground every step in their actual work |
| "I'll lose control" | Emphasize HITL and where their judgment matters |
| "I'm not technical enough" | Start with copy-paste commands, build confidence |
Build the workbook to address their specific resistance, not generic objections.
The Delegation Framework (Optional)
Use when the learner tends to do everything themselves.
| Marker | Meaning | Learner Action |
|---|---|---|
| 🤖 Let Claude work | Claude handles entirely | Prompt and wait |
| 👁️ Review this | Claude generated, verify | Check accuracy |
| 🧠 Your call | Only learner knows | Apply judgment |
Sprinkle these throughout steps to teach the pattern implicitly.
Where Each Applies
🤖 Let Claude work:
- •File/folder creation
- •Scaffolding and structure
- •Formatting and consistency
- •Research gathering
- •Generating exports
👁️ Review this:
- •Technical accuracy
- •Hallucination checks
- •"Does this actually work?"
- •Real-world applicability
🧠 Your call:
- •Strategic decisions
- •Priority and sequencing
- •What's missing from experience
- •Whether something belongs at all
Workbook Template
markdown
# Workbook: [Title] *A hands-on guide for [Learner]* --- ## What You're Building [2-3 sentences: End state and why it matters to them] --- ## Step 1: Prep **What you're doing:** [One line] ### Do This [Numbered actions] ### ✓ Ready for Step 2 when: [Self-verifiable gate] --- ## Step 2: [Foundation Step] **What you're doing:** [One line] ### Do This [Actions + sample prompt] ### Sample Prompt [Deliberately imperfect prompt] ### ✓ Ready for Step 3 when: [Gate] --- [Continue pattern for Steps 3-N] --- ## Step N: Make It Yours **What you're doing:** Ongoing refinement. ### Things to improve over time - [Bullet points of evolution paths] ### Questions to ask yourself - [Reflection prompts] --- ## Quick Reference [Folder structure, command cheatsheet, or summary table] --- *End of workbook*
Creating a New Workbook
When asked to create a workbook:
- •
Clarify the learner
- •Who is this for?
- •What do they already know?
- •What's their likely resistance?
- •
Clarify the end state
- •What should they have/be able to do when done?
- •Is it a tool, a workflow, or a mindset shift?
- •
Map the arc
- •What's the smallest first win?
- •What concepts need explaining?
- •Where will they need to iterate?
- •
Write gates first
- •Define success for each step before writing the step
- •Ensures steps are concrete, not vague
- •
Write sample prompts
- •Make them good enough to work
- •Leave room for learner improvement
- •
Address resistance
- •Build in checkpoints or frameworks that counter their specific hesitation
Quality Checklist
Before delivering a workbook:
- • Every step has a self-verifiable gate (except final)
- • Sample prompts are functional but imperfect
- • End state is agentic (tool, workflow, or mindset)
- • Learner's resistance is addressed
- • Steps build incrementally (no big jumps)
- • Quick reference section for ongoing use
- • Total steps between 8-12