Content
71%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.
A highly actionable, well-sequenced interactive skill with an executable helper script, a concrete bottom-up research recipe, and a usable output template. Its weaknesses are concentrated conciseness padding (framework definitions Claude already knows) and two dangling file references that undermine progressive disclosure.
Suggestions
Trim the "Key Concepts" section to non-obvious domain guidance only (the bottom-up recipe, Fact/Inference/Assumption labeling, capture-rate trick) and drop the TAM/SAM/SOM term definitions, "Why This Works", and anti-patterns that restate known concepts; also remove the Purpose paragraph that duplicates the frontmatter intent.
Resolve the broken references by creating `template.md` and `examples/sample.md` (or removing the pointers) — currently "Use `template.md` for the full fill-in structure" and "See `examples/sample.md`" point to files that don't exist, while the output template is inlined in the body.
Add an explicit validate-and-revise loop to the main interactive flow (e.g., "if TAM disagrees with third-party reports by >2x, revisit the population or ARPU assumption and recompute") rather than only posing validation questions to the user.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient, but the "Key Concepts" section defines TAM/SAM/SOM and explains "Why This Works" / anti-patterns that Claude already knows, and the Purpose paragraph duplicates the frontmatter intent verbatim — several padded sections that could be trimmed. | 3 / 5 |
Actionability | It provides a copy-paste-ready, verified-executable helper command ("python3 scripts/market-sizing.py --population 5400000 --arpu 1000 --sam-share 30% --som-share 10%"), a concrete bottom-up recipe with named sources, a fill-in output template, and enumerated questions with cited data covering the common cases. | 5 / 5 |
Workflow Clarity | A clear Step 0 → Questions 1-4 → Output sequence is present with a validation checklist and Mode 3's "validate against two independent analyst reports" checkpoint, but the main interactive flow lacks an explicit validate→fix→retry feedback loop, leaving a minor validation gap. | 4 / 5 |
Progressive Disclosure | Section structure is reasonable and the helper script reference resolves to a real file, but the body references `template.md` and `examples/sample.md` which do not exist in the bundle, and the ~90-line output template is inlined where `template.md` is said to live — references are signaled but broken, and content that should be separate is inline. | 3 / 5 |
Total | 15 / 20 Passed |