CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-strategy

Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pm-product-strategy/skills/product-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers a well-structured, actionable canvas template with a clear sequenced output process including a coherence-validation step, and appropriately pushes templates and further reading to clearly labeled external links. Its main weakness is token redundancy: the Metadata section duplicates the frontmatter and the Notes section restates three steps of the Output Process.

Suggestions

Delete the 'Metadata' section — it duplicates the frontmatter name, description, and triggers without adding information.

Merge the 'Notes' section into the Output Process or trim it, since 'Validate strategy coherence', 'Identify what must be true', and 'Propose validation experiments' already appear as steps 10-12.

Consider adding a brief worked example (e.g., one filled-in value proposition or North Star Metric) to lift actionability from concrete guidance to fully copy-paste-ready patterns.

DimensionReasoningScore

Conciseness

The canvas template and output process are tight, but the 'Metadata' section duplicates the frontmatter name/description/triggers verbatim in purpose, and the 'Notes' section restates Output Process steps 10-12 ('Validate strategy coherence', 'critical hypotheses', 'validation experiments') — several redundant/padded sections matching anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'). Not 4, because the duplication is noticeable rather than a minor instance.

3 / 5

Actionability

As an instruction-only skill it provides concrete, specific guidance: a 12-step Output Process, per-section guiding questions ('What before/How/What after/Alternatives' value-prop format, 'North Star Metric', 'OMTM'), and enumerated deliverables — matching anchor 4 ('mostly executable guidance... with minor gaps'). Not 5 because there is no worked example of a completed canvas and the output template is delegated to an external PPTX link.

4 / 5

Workflow Clarity

The Output Process is a clearly sequenced 12-step list that includes an explicit validation step ('Validate strategy coherence: ensure elements reinforce each other') and hypothesis/experiment surfacing, matching anchor 4 ('clear sequence with most checkpoints present'). This is a generative, non-destructive task so no validation cap applies; it falls short of anchor 5 because there are no feedback loops or error-recovery checkpoints.

4 / 5

Progressive Disclosure

With no bundle files present, the body is organized into well-labeled sections and keeps external material in clearly signaled one-level-deep 'Templates' and 'Further Reading' links rather than inlining it — matching anchor 4 ('good structure; most content appropriately placed; references mostly clear; minor organization gaps'), with the redundant Metadata block being the main gap.

4 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description that clearly states both the deliverable (a 9-section Product Strategy Canvas with all sections enumerated) and explicit, natural trigger conditions. Its only weaknesses are a single-action framing and slightly broad 'strategic plan'/'product direction' triggers that create minor overlap with general planning skills.

DimensionReasoningScore

Specificity

Names the concrete artifact ('9-section Product Strategy Canvas') and enumerates all nine sections ('vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility'), but offers only one action ('Create a comprehensive product strategy') rather than multiple distinct actions, matching anchor 4 ('several specific actions; minor gaps') rather than 5.

4 / 5

Completeness

It explicitly answers both questions: what ('Create a comprehensive product strategy using the 9-section Product Strategy Canvas' with all sections enumerated) and when ('Use when building a product strategy, creating a strategic plan, or defining product direction') with concrete trigger phrases, exactly matching anchor 5. A 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

The 'when' clause includes natural phrases users would say ('building a product strategy, creating a strategic plan, or defining product direction') plus the distinctive 'strategy canvas', but misses common synonyms like 'product plan', 'go-to-market strategy', or 'product roadmap' adjacent phrasing, fitting anchor 4 ('good keyword coverage; a few natural terms missing').

4 / 5

Distinctiveness Conflict Risk

The Product Strategy Canvas framing carves out a clear niche distinct from roadmap, PRD, or generic planning skills, though the broad trigger 'creating a strategic plan' creates minor overlap risk with business-strategy or planning skills, matching anchor 4 ('mostly distinct; minor overlap risk').

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-product-strategy/skills/product-strategy/SKILL.md

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.