product-strategist
Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling. Use for strategic planning, goal alignment, competitive analysis, and organizational design.
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-skills --skill product-strategistOverall
score
63%
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
67%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 provides a reasonable foundation with clear what/when structure and relevant domain terminology. However, it relies on somewhat abstract capability categories rather than concrete actions, and the trigger terms could overlap with other business strategy skills. The description would benefit from more specific deliverables and additional natural language variations.
Suggestions
Add more concrete action examples like 'generate quarterly OKR documents', 'create competitive landscape matrices', or 'design team org charts' to improve specificity.
Expand trigger terms to include common variations users might say: 'roadmap', 'product strategy', 'KPIs', 'quarterly goals', 'headcount', 'org structure', 'product vision document'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (product leadership) and lists several actions (OKR cascade generation, market analysis, vision setting, team scaling), but these are somewhat high-level categories rather than concrete specific actions like 'create quarterly OKR documents' or 'generate competitive landscape matrices'. | 2 / 3 |
Completeness | Clearly answers both what (OKR cascade generation, market analysis, vision setting, team scaling) and when ('Use for strategic planning, goal alignment, competitive analysis, and organizational design'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'OKR', 'market analysis', 'strategic planning', 'competitive analysis', but missing common variations users might say such as 'roadmap', 'product strategy', 'KPIs', 'quarterly goals', 'headcount planning', or 'org structure'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'Head of Product' and 'OKR cascade' are somewhat distinctive, terms like 'strategic planning', 'market analysis', and 'competitive analysis' could overlap with general business strategy skills, marketing skills, or executive planning tools. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured at a high level, but lacks the actionable depth needed for effective use. It describes capabilities without demonstrating them through examples, and provides no workflow guidance for the multi-step OKR cascade process it claims to support.
Suggestions
Add a concrete example showing sample input (company OKRs) and expected output (cascaded team OKRs with alignment scores)
Define a clear workflow sequence: 1) Input company strategy, 2) Generate cascade, 3) Review alignment scores, 4) Iterate if scores below threshold
Include validation criteria for what constitutes good alignment scores and how to fix misalignment
Link to or create reference files for each core capability (e.g., MARKET_ANALYSIS.md, VISION_FRAMEWORKS.md)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, listing capabilities and script usage without unnecessary explanation. No verbose descriptions of concepts Claude already knows. | 3 / 3 |
Actionability | Provides a concrete command with parameters and describes outputs, but lacks executable code examples, sample input/output, or copy-paste ready snippets showing actual OKR generation. | 2 / 3 |
Workflow Clarity | No workflow sequence is provided. The skill mentions cascading OKRs but doesn't explain the multi-step process, validation checkpoints, or how to verify alignment scores are correct. | 1 / 3 |
Progressive Disclosure | Content is brief and organized with clear sections, but references a script without linking to detailed documentation. No references to additional files for advanced features or examples. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
63%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 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 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.