product-strategy
Chief Product Officer expertise with proven frameworks and strategic guidance. Use when discussing product strategy, market analysis, competitive positioning, feature prioritization, or business models to apply expert CPO perspective.
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill product-strategy62
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 description has strong completeness with an explicit 'Use when...' clause and good trigger term coverage. However, it lacks specificity in describing concrete actions (what frameworks? what outputs?) and uses somewhat abstract language like 'proven frameworks' and 'strategic guidance' without elaboration. The description would benefit from listing specific deliverables or methodologies.
Suggestions
Replace vague phrases like 'proven frameworks and strategic guidance' with specific actions such as 'Creates product roadmaps, conducts TAM/SAM/SOM analysis, builds prioritization matrices'
Add concrete outputs or deliverables to improve specificity, e.g., 'Generates competitive landscape analyses, pricing strategies, and go-to-market plans'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CPO expertise) and mentions several areas (product strategy, market analysis, competitive positioning, feature prioritization, business models), but these are high-level categories rather than concrete actions. Missing specific verbs describing what the skill actually does. | 2 / 3 |
Completeness | Clearly answers both what (CPO expertise with frameworks and strategic guidance) and when (explicit 'Use when...' clause listing five specific trigger scenarios). The when clause is explicit and actionable. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'product strategy', 'market analysis', 'competitive positioning', 'feature prioritization', 'business models' are all phrases users would naturally use when seeking this type of guidance. | 3 / 3 |
Distinctiveness Conflict Risk | While 'CPO expertise' is somewhat distinctive, terms like 'product strategy' and 'business models' could overlap with general business consulting or startup skills. The CPO framing helps but isn't fully unique. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a marketing document for a CPO persona than actionable guidance. It lists many frameworks and concepts Claude already knows without providing concrete examples, templates, or specific instructions for applying them. The content would benefit significantly from executable examples showing actual analysis outputs rather than describing what analysis should contain.
Suggestions
Replace framework descriptions with concrete examples showing actual analysis output (e.g., a sample TAM/SAM/SOM calculation with numbers and reasoning)
Add specific templates or prompts for each analysis type rather than just listing steps (e.g., 'For competitive analysis, structure response as: [actual template]')
Remove explanations of well-known frameworks (JTBD, Lean Startup, Hook Model) and instead show how to apply them with worked examples
Add decision criteria for when to use each framework or analysis approach, with validation checkpoints to verify analysis quality
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary padding like the persona description ('shipped products used by millions', 'Led teams from 5 to 500') and explains frameworks Claude already knows (Jobs-to-be-Done, Lean Startup, Hook Model). However, it's reasonably organized and not excessively verbose. | 2 / 3 |
Actionability | The content is almost entirely abstract and descriptive rather than instructive. It lists frameworks and concepts but provides no concrete examples, specific prompts, actual analysis templates, or executable guidance. Phrases like 'Calculate TAM/SAM/SOM' and 'Create detailed personas' describe what to do without showing how. | 1 / 3 |
Workflow Clarity | The skill provides numbered lists suggesting sequence (e.g., Market Analysis steps 1-5), but lacks validation checkpoints, decision criteria, or feedback loops. There's no guidance on when to apply which framework or how to verify analysis quality. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections with headers, but everything is inline in one file. For a skill of this scope covering multiple frameworks and analysis types, some content could be split into separate reference files. No external references are provided. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
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.