CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

discovery-process

Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/discovery-process/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 workflow is well-sequenced with strong decision checkpoints and largely actionable phase guidance, but it is verbose with redundant restatements and its progressive disclosure is undermined by references to bundle files that are not actually provided.

Suggestions

Remove redundancy: drop the verbatim Purpose duplication of the intent field, and either cut the References section or the inline per-phase skill citations rather than maintaining both.

Provide the missing referenced files (template.md, examples/sample.md) or remove the dangling references so navigation is not broken.

Trim the 'What is the Discovery Process' and 'Why This Works' conceptual explanations, which cover knowledge Claude already has, to tighten token efficiency.

DimensionReasoningScore

Conciseness

The per-phase guidance is specific, but the body carries notable redundancy: the Purpose section duplicates the intent frontmatter, the References section re-lists every skill path already cited inline, and the end-to-end summary tree re-sequences the phases; 'Why This Works' and 'What is the Discovery Process' also explain concepts Claude largely already knows.

3 / 5

Actionability

Each phase gives concrete actionable guidance — named component skills to invoke, participant lists, durations, output formats, sample interview questions, a structured note template, and specific experiment types (concierge, prototype, landing page, A/B) — with only minor gaps where execution depends on the referenced skills' contents.

4 / 5

Workflow Clarity

Six phases are sequenced with day/week timing and three explicit decision points (context-to-start, saturation, validation) that branch into yes/no paths with time impacts and recovery actions, providing clear feedback loops for the process.

5 / 5

Progressive Disclosure

References are clearly signaled and one level deep, but no bundle files exist alongside the skill, so referenced paths like 'template.md', 'examples/sample.md', and 'skills/*/SKILL.md' point to non-existent files, and the full 6-phase detail plus the repeated references list are inlined rather than split into separate materials.

3 / 5

Total

15

/

20

Passed

Description

75%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 cleanly answers both what and when with a clear domain niche and decent trigger-term coverage. It is slightly abstract in its 'when' clause and could add concrete scenario triggers and synonyms to reach the top level.

Suggestions

Make the 'when' clause more concrete with scenario-based triggers (e.g., 'Use when activation dropped and you need to find out why, or before committing to a roadmap item').

Add natural synonyms such as 'customer research', 'product discovery', or 'assumption validation' to broaden trigger-term coverage.

Enumerate the remaining phases (solution generation, decide & document) so the capability list is comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('discovery cycle from problem hypothesis to validated solution') and several concrete sub-actions ('framing, interviews, synthesis, and experiments'), with only minor coverage gaps such as solution generation and decision documentation not enumerated.

4 / 5

Completeness

Explicitly states both what ('Run a full discovery cycle from problem hypothesis to validated solution') and when ('Use when a team needs a structured path through framing, interviews, synthesis, and experiments'); the 'when' is present but slightly abstract rather than scenario-specific trigger phrases.

4 / 5

Trigger Term Quality

Includes natural terms a user might say ('discovery cycle', 'problem hypothesis', 'interviews', 'synthesis', 'experiments') with good coverage, though common synonyms like 'customer research' or 'product discovery' are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (product discovery cycle) with distinct triggers, though it could overlap with adjacent research or interview-related skills, leaving minor conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (517 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

deanpeters/Product-Manager-Skills

Path

skills/discovery-process/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.