Name: product-discovery
Rating: 57.599999999999994 (1 reviews)
Author: alirezarezvani

product-discovery

Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/product-discovery/SKILL.md

The canonical home for this skill is product-discovery in alirezarezvani/claude-skills

Quality

Content

71%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 well-organized, concise discovery playbook with actionable techniques and a clear workflow, but it references a script and a reference file that are not present in the bundle, undermining progressive disclosure.

Suggestions

Ship the referenced `scripts/assumption_mapper.py` and `references/discovery-frameworks.md`, or remove the dangling references and inline the essential content.

Add an explicit validate/retry checkpoint in the workflow (e.g., review synthesized evidence against the success threshold before the stakeholder decision) to strengthen feedback loops.

Tighten the assumption-category shorthand lines or move them into the referenced framework file to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is largely lean bullet-style content that assumes Claude knows discovery concepts (it names Teresa Torres OST, assumption categories) without padding; only minor shorthand lines like "Desirability: users want this" could be trimmed.	4 / 5
Actionability	Concrete guidance throughout: an executable command (`python3 scripts/assumption_mapper.py assumptions.csv`), named techniques (fake door/concierge tests, journey friction mapping), and a specific 10-day sprint structure; minor gaps in how-to detail for the interview/synthesis steps.	4 / 5
Workflow Clarity	A clear 6-step Core Discovery Workflow is sequenced with decision checkpoints ("Reject weak opportunities early", end with "proceed, pivot, or stop"); validation/explicit feedback loops could be more pronounced, but the operations are not destructive or batch-heavy so no cap applies.	4 / 5
Progressive Disclosure	The body is well-sectioned and signals one-level-deep references (`scripts/assumption_mapper.py`, `references/discovery-frameworks.md`), but those bundle files do not exist on disk, so the navigation points to dangling paths rather than a real split of content.	3 / 5
	Total	15 / 20 Passed

Description

61%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 a strong, natural trigger clause but functions primarily as a "when" statement; it lacks an explicit statement of what the skill does or produces. It is distinctive and uses natural terminology well.

Suggestions

Add an explicit "what" clause before the trigger, e.g. "Facilitate structured product discovery to de-risk bets. Use when ...".

Surface concrete outputs the skill produces (e.g., opportunity trees, prioritized assumption test plans, sprint decision artifacts) to lift specificity and completeness.

Dimension	Reasoning	Score
Specificity	Names the discovery domain and lists concrete trigger activities ("validating product opportunities, mapping assumptions, planning discovery sprints, ... testing problem-solution fit"), but describes when rather than what the skill does, leaving capabilities implicit.	3 / 5
Completeness	Has an explicit "Use when..." clause for the "when", but the "what" is only weakly implied through gerund triggers rather than an explicit capability statement, so it falls short of the both-what-and-when anchors.	3 / 5
Trigger Term Quality	Strong coverage of natural discovery phrases a practitioner would say ("product opportunities", "assumption mapping", "discovery sprints", "problem-solution fit"), with only minor synonyms missing.	4 / 5
Distinctiveness Conflict Risk	The discovery-specific triggers (opportunities, assumptions, sprints, problem-solution fit) carve a clear niche with minimal overlap risk, though it could slightly overlap with general research/strategy skills.	4 / 5
	Total	14 / 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: 3 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/product-discovery/SKILL.md
Commit: 19392f7

Reviewed: ~3 hours 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.