Content
26%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a conceptual overview of JTBD rather than a working skill: it explains what the framework is (which Claude already knows), lists when to use it, and cites books, but provides no executable method, templates, or sequenced process for actually doing JTBD work. Its strongest aspect is compact, headed structure with no bundle sprawl. The main fixes are to cut the primer/fluff and replace it with concrete JTBD working materials.
Suggestions
Replace the 'What It Is' primer with executable JTBD working materials: a job-story template ('When [situation], I want to [motivation], so I can [expected outcome]'), a starter interview question bank, and the four forces of progress (push, pull, anxiety, habit).
Add a sequenced workflow with checkpoints, e.g., 1. identify the struggling moment from the user's context, 2. map the four forces for the customer, 3. draft job stories, 4. validate them against churn or switching data if available.
Delete the 'Domain Context' and 'Input Requirements' sections and the JTBD-101 explanation — Claude already knows the framework, and the reclaimed tokens should fund the missing method; merge 'Resources' and 'Further Reading' into one section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Several sections are unnecessary: 'Domain Context' is padded fluff ('combines best practices from industry leaders', 'proven product management framework') and 'What It Is' re-explains JTBD basics Claude already knows ('people don't buy products, they hire them to make progress in their lives'), plus a largely filler 'Input Requirements' list. Scored 2 rather than 3 because roughly half the body could be deleted without losing actionable information. | 2 / 5 |
Actionability | The only operational guidance is a single high-level reframe — 'Move from asking "What do customers want?" to asking "What progress are customers trying to make?"' — with no job-story template, interview questions, forces-of-progress mapping, or analysis steps. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute' (2); not 1 because one actionable reframe and explicit applicability conditions ('When Not to Use It') are given. | 2 / 5 |
Workflow Clarity | No sequence of steps exists anywhere in the body — it describes the framework and when/when-not to apply it but never instructs how to proceed (e.g., prepare an interview, map forces, draft job stories). This matches anchor 1 ('steps missing; no sequence'); the simple-skill exception doesn't apply because the intended action is not unambiguous, and anchor 2 requires at least a rough sequence, which is absent. | 1 / 5 |
Progressive Disclosure | The body is ~50 lines with no bundle files and clearly headed sections ('What It Is', 'When to Use It', 'When Not to Use It', 'Further Reading' with a single one-level external link), satisfying the short-skill guideline. Minor organization gaps — duplicate heading hierarchies (H2 sections before a mid-document H1) and separate 'Resources' and 'Further Reading' sections that fragment the same content — keep it at 4 rather than 5. | 4 / 5 |
Total | 9 / 20 Passed |