Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a thorough, well-sequenced, and actionable market-sizing workflow with strong validation checkpoints. Its main weakness is conciseness, due to redundant boilerplate sections, and the lack of any progressive-disclosure structure splitting the long monolithic document.
Suggestions
Remove the generic 'Instructions' section and the duplicative 'What This Command Does' list, since they restate the detailed steps that follow.
Trim the templated 'Use this skill when / Do not use this skill when' boilerplate, which adds tokens without domain-specific value.
Consider moving the lengthy 9-section report template and per-business-model TAM formulas into a reference file (e.g. references/report-template.md) to improve progressive disclosure and reduce the SKILL.md footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core step-by-step methodology is useful, but the body is padded with redundant boilerplate such as the generic 'Instructions' bullets and the 'What This Command Does' list that duplicates the later detailed steps, fitting the 'mostly efficient but includes some unnecessary explanation' anchor. | 2 / 3 |
Actionability | The skill provides concrete formulas (TAM = Σ (Segment Size × ACV); SAM = TAM × Geographic % × Product Fit % × Market Readiness %), specific SOM percentages (Year 3: 2-3%, Year 5: 4-6%), named data sources, and a full 9-section report template, giving actionable, copy-ready guidance. | 3 / 3 |
Workflow Clarity | The process is sequenced across nine explicit steps with validation checkpoints, including the 'If variance > 30%, investigate and explain differences' feedback loop and a dedicated 'Validation and Sanity Checks' section, matching the clear-sequence-with-explicit-validation anchor. | 3 / 3 |
Progressive Disclosure | The body is well-organized into sections but is a monolithic single file with no bundle files in references/, scripts/, or assets/ and no one-level-deep references, so content that could be split out remains inline, fitting the 'some structure but content that should be separate is inline' anchor. | 2 / 3 |
Total | 10 / 12 Passed |