Creates product strategies using Crossing the Chasm, Playing to Win, and strategic canvas frameworks. Use when defining where to play and how to win, choosing beachhead markets, or connecting tactics to strategy.
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It names specific strategic frameworks, uses natural terminology that strategists would recognize, includes an explicit 'Use when' clause with multiple trigger scenarios, and carves out a distinct niche through framework-specific language that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates product strategies', names three specific frameworks (Crossing the Chasm, Playing to Win, strategic canvas), and describes concrete strategic activities (defining where to play, choosing beachhead markets, connecting tactics to strategy). | 3 / 3 |
Completeness | Clearly answers both what (creates product strategies using specific frameworks) AND when (explicit 'Use when' clause with three distinct trigger scenarios: defining where to play/how to win, choosing beachhead markets, connecting tactics to strategy). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'product strategies', 'Crossing the Chasm', 'Playing to Win', 'where to play', 'how to win', 'beachhead markets', 'tactics to strategy'. These are terms strategists and product managers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers around specific strategic frameworks (Crossing the Chasm, Playing to Win) and terminology (beachhead markets, where to play/how to win). Unlikely to conflict with generic business or product skills due to framework-specific language. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that efficiently presents two strategic frameworks with a usable template. The main weakness is the lack of concrete examples showing completed strategy outputs and missing validation steps for verifying strategic choices. The skill tells Claude what to produce but not how to evaluate if the output is good.
Suggestions
Add a concrete example of a completed Product Strategy template (e.g., for a fictional SaaS product) to show what good output looks like
Include validation criteria or questions to verify strategic choices (e.g., 'How do you know the beachhead is right? Check: Is it small enough to dominate? Do you have access to buyers?')
Add specific decision criteria for the 'Where to Play' choice beyond just listing segments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting frameworks and templates without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides a concrete template structure with clear placeholders, but the guidance remains somewhat abstract. The template shows what to fill in but lacks specific examples of completed strategies or concrete decision criteria. | 2 / 3 |
Workflow Clarity | The checklist provides a sequence of steps, but there are no validation checkpoints or feedback loops. For strategy work, there's no guidance on how to verify choices are correct or iterate when assumptions prove wrong. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the content is well-organized with clear sections. The structure moves logically from frameworks to templates to quick reference, with no need for external file references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
53530ef
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.