CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pmf-check

Diagnoses product-market fit from survey, usage and pipeline data and returns a scored verdict with the next moves. Use when you ask 'do we have product-market fit', 'is our PMF survey good enough', 'what does 35% very disappointed mean', 'should we scale yet', 'why is growth stalling', or need a Sean Ellis survey, retention check, or PMF level read. Draws on 137 insights from 66 Lenny's Podcast guests incl. Sean Ellis, Todd Jackson and Rahul Vohra.

Quality

92%

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

88%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 high-quality, expert-driven skill body: nearly every line carries a specific threshold, benchmark, or named-source rule, and the diagnose-route-deliver workflow is unambiguous with explicit done-when gates. The main improvements are removing the duplication between the inline Receipts section and references/quotes.md, and moving the long grading table to a reference to slim the main file.

Suggestions

Drop or shorten the inline Receipts section since references/quotes.md already serves verified quotes with timestamps; keep at most one exemplar quote in the body.

Move the 8-criterion grading table to references/frameworks.md (or a new grading reference), keeping in the body only the instruction to grade 1-5 per criterion and total out of 40.

The 'Go deeper' related-skills list is useful, but consider trimming the one-line rationale per skill to a short parenthetical to save tokens.

DimensionReasoningScore

Conciseness

The body is dense with expert-specific data (thresholds, benchmarks, named sources) and contains no padding over concepts Claude already knows. Minor trimming is possible: the Receipts section duplicates content already in references/quotes.md, and the 8-criterion grading table is bulk inlined.

4 / 5

Actionability

Fully actionable for an instruction-only skill: verbatim survey questions, exact thresholds ('40%', '30-response floor', 'free 60% / paid 20-30%'), numbered play steps, a copy-paste-ready deliverable template, and a grading rubric with explicit 1/3/5 anchors covering the common cases.

5 / 5

Workflow Clarity

The sequence is explicit — diagnose (max 4 questions) → routing table → numbered plays → filled-in deliverable — with validation checkpoints ('Done when you can state: the score, n, the highest-scoring segment...'), confidence scaffolding, and a re-run feedback loop in Play B. Not a destructive/batch skill, so no hard cap applies.

5 / 5

Progressive Disclosure

Good structure with clearly signaled one-level-deep references ('references/frameworks.md - every framework in this skill, how to run it'; 'references/quotes.md - verified quotes with timestamps'), both verified to exist with real content and no nested references. Held below 5 because the Receipts section duplicates quotes.md inline and the full grading table and deliverable template are bulk content that could live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

91%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, concrete about inputs and outputs, with an explicit 'Use when' clause carrying directly quoted natural-language triggers. The only refinement available is broader coverage of the skill's secondary capabilities and slightly narrowing the broadest triggers ('why is growth stalling') that could overlap adjacent growth skills.

Suggestions

Mention one secondary capability, e.g. 'grades an existing PMF survey or board slide against expert criteria', to close the coverage gap.

Qualify 'why is growth stalling' with PMF context (e.g. 'why is growth stalling despite a passing PMF score') to reduce overlap with general growth-analytics skills.

DimensionReasoningScore

Specificity

'Diagnoses product-market fit from survey, usage and pipeline data and returns a scored verdict with the next moves' names concrete inputs and outputs in third person, listing several specific actions. Not 5: coverage gaps remain (no mention of grading existing PMF analyses or building the half-and-half roadmap); not 3: it goes well beyond naming a domain plus one action.

4 / 5

Completeness

Explicitly answers both what ('Diagnoses product-market fit from survey, usage and pipeline data and returns a scored verdict with the next moves') and when ('Use when you ask...', followed by concrete trigger phrases) — matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers users would actually say, quoted directly: 'do we have product-market fit', 'is our PMF survey good enough', 'what does 35% very disappointed mean', 'should we scale yet', 'why is growth stalling', plus synonyms like 'Sean Ellis survey', 'retention check', and 'PMF level read'.

5 / 5

Distinctiveness Conflict Risk

A clear PMF-diagnosis niche with distinctive triggers (Sean Ellis survey, '35% very disappointed', PMF level read). Not 5: 'why is growth stalling' and 'should we scale yet' could plausibly match a general growth-analytics or scaling skill; not 3: the PMF framing is unmistakable.

4 / 5

Total

18

/

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/pmf-check/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.