discovery-session

Start interactive product discovery with expert guidance

Quality

31%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/product-design/skills/discovery-session/SKILL.md

Quality

Content

39%

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

This skill has excellent workflow structure with clear sequencing through discovery phases, but suffers from severe verbosity. The full question templates and analysis frameworks bloat the file unnecessarily—Claude can generate contextually appropriate questions from brief guidance. The content would benefit greatly from splitting detailed question banks and analysis templates into separate reference files.

Suggestions

Move the 20 detailed question templates to a separate `discovery-questions.md` reference file, keeping only section summaries in the main skill

Replace verbose analysis framework bullets (✅ 💡) with a brief instruction like 'Provide validation, market insights, and improvement suggestions for each response'

Add executable code snippets for creating the discovery directory and saving session files

Condense the welcome message template to key points—Claude can generate appropriate welcoming language

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines with extensive templated content that Claude doesn't need spelled out. The full text of all 20 questions, example responses, and analysis frameworks could be condensed to a fraction of the size while preserving the same guidance.	1 / 3
Actionability	Provides concrete question templates and output file names, but lacks executable code for file creation/management. The 'Execution Instructions' are high-level directives rather than specific implementation steps.	2 / 3
Workflow Clarity	Clear sequential flow through 4 sections with 20 numbered questions. Session controls provide navigation options, and the welcome message sets expectations. The multi-step process is well-defined with explicit deliverables at the end.	3 / 3
Progressive Disclosure	Monolithic wall of text with all 20 questions fully expanded inline. The question templates, analysis frameworks, and output specifications should be split into separate reference files, with SKILL.md providing just the overview and flow.	1 / 3
	Total	7 / 12 Passed

Description

22%

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 is too vague and lacks the specificity needed for effective skill selection. It fails to explain what concrete actions the skill performs and provides no explicit trigger conditions. The phrase 'expert guidance' is marketing fluff that doesn't help Claude understand when to use this skill.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Conducts user persona development, prioritizes features using RICE framework, maps customer journey touchpoints')

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user mentions product discovery, user research, feature prioritization, or wants to define product requirements')

Include common variations of terminology users might say (e.g., 'product ideation', 'MVP definition', 'customer needs analysis', 'product roadmap')

Dimension	Reasoning	Score
Specificity	The description uses vague language ('interactive product discovery', 'expert guidance') without listing any concrete actions. It doesn't specify what actions are performed or what outputs are produced.	1 / 3
Completeness	The description weakly addresses 'what' (start interactive product discovery) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	'Product discovery' is a relevant domain keyword that users might say, but the description lacks common variations or related terms users would naturally use (e.g., 'user research', 'product requirements', 'feature prioritization', 'customer interviews').	2 / 3
Distinctiveness Conflict Risk	'Product discovery' provides some domain specificity, but 'interactive' and 'expert guidance' are generic enough that this could conflict with other coaching, consulting, or product-related skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 5 months 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.