CtrlK
BlogDocsLog inGet started
Tessl Logo

product-vision

Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders. Use when defining or refining a product vision, creating a vision statement, or aligning the team around a shared direction.

60

Quality

75%

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-vision/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 a compact, well-structured instruction-only skill with a clear process and output criteria. It is held back by frontmatter duplication, conceptual padding in Domain Context, and the absence of example vision statements.

Suggestions

Remove the 'Metadata' section (Name, Description, Triggers) since it duplicates the YAML frontmatter, or keep only the Triggers list there.

Cut or shrink 'Domain Context' to stop explaining what a product vision is; assume Claude's knowledge and keep only any non-obvious framing.

Add 1-2 short example vision statements (or a template) under Output so the brainstorming guidance is concrete rather than abstract.

DimensionReasoningScore

Conciseness

The Process, Output, and Notes sections are efficient, but the 'Domain Context' explains what a product vision is (a concept Claude already knows) and 'Metadata' duplicates the frontmatter name and description, adding unnecessary explanation that could be trimmed.

3 / 5

Actionability

The 6-step process gives concrete structure ('Draft multiple vision options (3-5 variations)', 'explain your rationale'), but as a brainstorming skill it lacks any example vision statements or templates that would make the guidance fully actionable.

3 / 5

Workflow Clarity

A clear linear 6-step sequence is present with a selection/rationale checkpoint at step 5; the task is non-destructive so no validation loop is required, but the checkpoint is implicit rather than an explicit validation step.

4 / 5

Progressive Disclosure

Sections are well organized and the 'Further Reading' external links are clearly signaled one level deep, but the 'Metadata' section duplicates frontmatter, a minor organization gap that keeps it below a 5.

4 / 5

Total

14

/

20

Passed

Description

78%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 strong: it cleanly states both the capability and an explicit 'Use when' trigger with natural synonyms. Its only weakness is modest action specificity and slight overlap with adjacent product-management domains.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ('Brainstorm ... product vision', 'creating a vision statement') but does not list several specific actions, fitting the anchor-3 example rather than the multi-action anchor 4.

3 / 5

Completeness

It explicitly answers both what ('Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders') and when ('Use when defining or refining a product vision, creating a vision statement, or aligning the team around a shared direction') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural keywords are present with synonyms ('product vision', 'vision statement', 'refining a product vision'), but a few common variations such as 'north star vision' appear only in the body, not the description, so it is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Product vision' and 'vision statement' form a clear niche with distinct triggers, but there is minor overlap risk with closely related product-management skills such as strategy, roadmap, or objectives work.

4 / 5

Total

16

/

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