product-strategist

Strategic product leadership toolkit for Head of Product covering OKR cascade generation, quarterly planning, competitive landscape analysis, product vision documents, and team scaling proposals. Use when creating quarterly OKR documents, defining product goals or KPIs, building product roadmaps, running competitive analysis, drafting team structure or hiring plans, aligning product strategy across engineering and design, or generating cascaded goal hierarchies from company to team level.

1.08x

Quality

87%

Does it follow best practices?

Impact

97%

1.08x

Average score across 6 eval scenarios

Securityby

—

The risk profile of this skill

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a well-sequenced workflow and properly structured references to real bundle files. Its main weakness is conciseness — repeated command listings and a large inline dashboard example inflate the token budget without adding proportionate guidance.

Suggestions

Consolidate the repeated invocation examples: keep one canonical Quick Start block and have Step 3 and the Usage section reference it rather than restating the same commands.

Move the full ASCII dashboard output example into a reference file (e.g. references/examples/) and keep only a short illustrative snippet inline.

Add an explicit feedback loop in Step 4/5 such as 'if overall alignment <80%, adjust teams/contribution in Step 3 and re-run the generator'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept-explanation padding, but the same base command (e.g. 'python scripts/okr_cascade_generator.py growth') recurs across Quick Start, Step 3, and the Usage section, and the inline ASCII dashboard block (~35 lines) could be trimmed or referenced.	3 / 5
Actionability	Fully executable, copy-paste-ready commands with flags (--teams, --contribution, --json, --metrics), a defaults table, and concrete output examples covering the common cases.	5 / 5
Workflow Clarity	A clear 5-step sequence with an alignment-score review checkpoint (Step 4 'Action if Below') and a validation checklist (Step 5); minor gap is that the 'fix and re-run' feedback loop is implied rather than an explicit 'return to Step 3' instruction.	4 / 5
Progressive Disclosure	Good structure with one-level-deep, clearly signaled references (strategy_types.md, okr_framework.md, examples/sample_growth_okrs.json — all verified present); minor gaps are the heavy inline output examples and the unreferenced assets/okr_template.md bundle file.	4 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is excellent: third-person, specific, and explicitly pairs concrete capabilities with a rich 'Use when' trigger clause. It scores at the top of every dimension with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'OKR cascade generation, quarterly planning, competitive landscape analysis, product vision documents, and team scaling proposals' — giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both 'what' (strategic product leadership toolkit covering five named capabilities) and 'when' ('Use when creating quarterly OKR documents...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases users would say include 'quarterly OKR documents', 'product goals or KPIs', 'product roadmaps', 'competitive analysis', 'team structure or hiring plans', and 'cascaded goal hierarchies' — broad and varied coverage.	5 / 5
Distinctiveness Conflict Risk	A clear niche for a 'Head of Product' with distinct OKR/strategy triggers, minimal overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: product-team/skills/product-strategist/SKILL.md
Commit: 19392f7

Reviewed: 29 minutes ago

Table of Contents

Discovery Implementation Validation

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.