CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

customer-interviews

Designs customer interviews and turns the transcripts into decisions. Produces an interview guide plus a synthesis (forces of progress, jobs, pathways, opportunities) you can paste into a doc. Use for 'customer interviews', 'discovery calls', 'JTBD', 'switch interview', 'who should I talk to', 'how many interviews', 'synthesize these transcripts', or 'why do customers churn/buy'. Draws on 140 Lenny's Podcast guests incl. Teresa Torres, Bob Moesta and Judd Antin.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, information-dense skill body: it sequences a multi-path workflow, gives copy-paste scripts and templates, and points to real one-level-deep references. The gaps are minor — some duplicated quote content between the body and references/quotes.md, and no explicit self-validation step for its own output.

Suggestions

Drop or compress the 'Receipts' section in SKILL.md (its quotes already live in references/quotes.md) and keep a one-line pointer instead, saving body tokens.

Add a final step instructing Claude to run the 'Grade existing work' rubric against its own synthesis before presenting it, closing the workflow_clarity validation gap.

Consider moving the 8-criterion grading table to references/frameworks.md (with a short inline summary) so the body stays a lean overview.

DimensionReasoningScore

Conciseness

The body is dense with expert-attributed specifics (sample sizes, question scripts, stop rules) and never explains basics Claude already knows, so it clears level 3. It is not a 5 because the 'Receipts' section inlines long quotes that already live in references/quotes.md (e.g. the Moesta 00:12:34, Torres 39:57 and Todd Jackson 01:18:06 quotes appear in both), a trimmable duplication.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: verbatim prompts ('Tell me about the last time you [bought / switched / tried to do X]'), numeric recruiting/sample rules ('10 to 12 per round', 'stop when you can predict 70 to 80 percent of the next answer'), a fenced paste-ready deliverable template, and a 1/3/5 grading rubric covering common cases.

5 / 5

Workflow Clarity

A clear Step 1 Diagnose -> Step 2 Pick the play -> Step 3 Run it (A/B/C) sequence with routing gates ('No decision means do not run it') and feedback loops ('Predictions vs actual: what surprised us', say-do checks) — above level 3's implicit checkpoints. It falls short of 5 only because there is no explicit step validating the skill's own produced deliverable before hand-off; the 'Grade existing work' rubric is framed for user-supplied work, not self-check.

4 / 5

Progressive Disclosure

Clear sections with well-signaled, one-level-deep references that are real files ('references/frameworks.md — every framework in this skill, how to run it', 'references/quotes.md — verified quotes with timestamps'), matching level 4's 'mostly clear, minor gaps'. Not level 5: the receipts/quotes duplication between body and reference file, and sizable inline blocks (the grading table, red flags) that could be split out, show content is not cleanly 'appropriately split'.

4 / 5

Total

17

/

20

Passed

Description

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

An excellent description: third-person voice, concrete what-and-when with explicit trigger phrases, and a distinct niche. The only weakness is a handful of missing natural synonyms in the trigger list.

Suggestions

Add 'user interviews', 'customer research', and 'customer discovery' to the 'Use for' trigger list — these are among the most common phrasings for this intent and are currently absent.

Consider trimming 'Draws on 140 Lenny's Podcast guests incl. Teresa Torres, Bob Moesta and Judd Antin.' to a shorter provenance clause; it adds authority but few trigger keywords.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive output coverage: 'Designs customer interviews and turns the transcripts into decisions. Produces an interview guide plus a synthesis (forces of progress, jobs, pathways, opportunities) you can paste into a doc.' This matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage), not level 4, since no capability of the skill is left unnamed.

5 / 5

Completeness

Both questions are answered explicitly: what — 'Designs customer interviews and turns the transcripts into decisions. Produces an interview guide plus a synthesis…' and when — 'Use for 'customer interviews', 'discovery calls', 'JTBD'…' with concrete trigger phrases. This matches the level-5 anchor exactly; level 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

Trigger list is strong and phrased as natural user language ('customer interviews', 'discovery calls', 'JTBD', 'switch interview', 'who should I talk to', 'how many interviews', 'synthesize these transcripts', 'why do customers churn/buy'), but a few common variations are missing — notably 'user interviews', 'customer research', and 'discovery interview'. Good coverage with a few natural terms absent matches level 4, not level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (customer discovery interviewing / JTBD synthesis) with distinct triggers like 'switch interview', 'JTBD', and 'synthesize these transcripts' that no generic research or analytics skill would claim, matching level 5's minimal conflict risk. It sits above level 4 because even adjacent skills (validate-idea, prioritize, price) are disambiguated by the interview-specific framing.

5 / 5

Total

19

/

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

menkesu/awesome-pm-skills

Path

skills/customer-interviews/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.