CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

discovery-interview-prep

Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product ideas.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable with a clear sequenced flow and well-organized sections, but it is let down by verbosity: a verbatim duplication of the frontmatter intent and overlapping bias/pitfall sections inflate the token budget. Splitting the worked example or output template into a reference file would improve both conciseness and progressive disclosure.

Suggestions

Remove the verbatim duplication of the frontmatter intent in the Purpose section, or replace it with a single distinct sentence; the intent already appears in frontmatter.

Consolidate 'Biases to Avoid' (inside the output template) and 'Common Pitfalls' (standalone section) into one section to eliminate overlapping guidance.

Move the fully worked Mom Test example and/or the large interview-plan output template into a one-level-deep reference file (e.g. references/example-plan.md) to slim SKILL.md and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The ~400-line body duplicates the frontmatter intent verbatim in the Purpose section and repeats bias guidance in both the output template ("Biases to Avoid") and a standalone "Common Pitfalls" section, fitting 'mostly efficient but includes some unnecessary explanation'; it is not 4 because the redundancy exceeds minor over-explanation, and not 2 because most content is genuine domain-specific signal rather than padding.

3 / 5

Actionability

Copy-paste-ready question scripts ("Tell me about the last time you [experienced the problem]. What did you try?"), four enumerated options per question, and a fully worked Mom Test example match 'fully executable; copy-paste ready; specific examples cover the common cases'; it is not 4 because the worked example fills in every template placeholder for the primary use case.

5 / 5

Workflow Clarity

A clear Step 0 → Q1–Q4 → Output sequence with adaptation logic and a Success Criteria checklist matches 'clear sequence with most checkpoints present'; it is not 5 because there are no explicit validate-then-retry feedback loops, and not 3 because the steps are well-defined with adaptation guidance rather than gap-ridden.

4 / 5

Progressive Disclosure

Well-organized sections (Purpose, Input, Key Concepts, Application, Steps, Output, Examples, References) with clearly signaled one-level references to related skills (workshop-facilitation, problem-statement.md) match 'good structure; most content appropriately placed'; it is not 5 because a 400-line skill could offload the large output template or worked example into one-level-deep reference files for a leaner SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

87%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 states a concrete planning action across four dimensions, includes an explicit 'Use when' clause with natural trigger scenarios, and occupies a distinct niche. The only weakness is moderate trigger-term breadth — a few common synonyms (user research, customer development) are missing.

DimensionReasoningScore

Specificity

Quotes "Plan customer discovery interviews with the right goal, segment, constraints, and method" name the domain plus four concrete planning dimensions, matching the 'several specific actions; minor gaps' anchor; it falls short of 5 because it rests on a single verb (Plan) rather than multiple distinct actions.

4 / 5

Completeness

It explicitly answers what ("Plan customer discovery interviews...") and when ("Use when preparing interviews for problem validation, churn research, or new product ideas") with concrete trigger phrases, matching the top anchor exactly; it is not 4 because the 'when' is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Natural phrases like "problem validation", "churn research", and "new product ideas" give good keyword coverage a user would actually say, matching the 'good coverage; a few natural terms missing' anchor; it is not 5 because synonyms like "user research" or "customer development" are absent.

4 / 5

Distinctiveness Conflict Risk

"customer discovery interviews" with triggers for problem validation, churn research, and new product ideas carves a clear niche with minimal overlap risk, matching the 'clear niche with distinct triggers' anchor; it is not 4 because the triggers are specific enough to avoid confusion with adjacent research skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

deanpeters/Product-Manager-Skills

Path

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