CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pmf-survey

Use when asked to "PMF survey", "measure product-market fit", "40% rule", "Sean Ellis test", "Rahul Vohra method", or "how disappointed would you be". Helps quantify product-market fit and systematically improve it. The PMF Survey framework (created by Sean Ellis, popularized by Rahul Vohra at Superhuman) measures how disappointed users would be without your product and turns that data into a roadmap.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pmf-survey/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%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 a well-organized concept overview rather than an operational skill: it explains what the PMF survey is and when to use it, but never instructs how to run the survey, segment responses, or generate the roadmap. The highest-value fixes are adding the concrete survey/analysis procedure and cutting the filler sections.

Suggestions

Add a step-by-step procedure for running the PMF survey: which users to sample (active users, not all signups), how to deliver the key question, and how to segment responses by the 'very disappointed' cohort.

Include the analysis workflow from the Rahul Vohra method — e.g., cross-tabulating 'very disappointed' responses against user characteristics to identify the highest-PMF segment and the themes that drive the roadmap — so the skill instructs rather than describes.

Remove the 'Domain Context' and 'Input Requirements' filler sections and merge the duplicate 'Resources' and 'Further Reading' lists to tighten token use.

DimensionReasoningScore

Conciseness

'This skill implements a proven product management framework. The approach combines best practices from industry leaders' is pure filler, and the 'What It Is' section re-explains the widely known Sean Ellis framework. Mostly efficient overall, so anchor 3 fits better than 2 — the 40% benchmark and when-to-use lists earn their place, but the filler sections and duplicated resource lists could be trimmed.

3 / 5

Actionability

The only concrete artifacts are the key question ('How would you feel if you could no longer use this product?'), the three response options, and the 40% threshold; there are no steps for sampling users, running the survey, analyzing responses, or generating the roadmap the description promises. Matches anchor 2 (high-level hints missing the specific steps) rather than 3, since no executable procedure exists at all.

2 / 5

Workflow Clarity

A rough implicit flow (ask the question → count 'very disappointed' → compare to 40% → build a roadmap) is reconstructable from the concept text, but it is never presented as a sequence and the analysis/roadmap steps are absent. Anchor 2 fits; anchor 1 would require even this implicit flow to be missing.

2 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are needed; sections are clearly headed and the body is short. Minor organization gaps — the pre-title 'Domain Context'/'Input Requirements' sections and the redundant 'Resources' vs 'Further Reading' lists — keep it at anchor 4 rather than 5.

4 / 5

Total

11

/

20

Passed

Description

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

A strong description: an explicit 'Use when' clause with excellent natural-phrase coverage and synonyms, a clear third-person statement of what the skill does, and a distinctive niche that is unlikely to trigger the wrong skill. The only gap is that the stated actions don't cover the full workflow (segmentation, tracking over time).

DimensionReasoningScore

Specificity

Concrete actions include 'quantify product-market fit', 'measures how disappointed users would be', and 'turns that data into a roadmap' — several specific actions with minor gaps (no mention of segmenting users or tracking PMF over time). Fits anchor 4 better than 3 (more than 1-2 actions) and short of 5's comprehensive coverage.

4 / 5

Completeness

Explicitly answers 'when' ('Use when asked to...') with concrete trigger phrases and 'what' ('Helps quantify product-market fit and systematically improve it... turns that data into a roadmap'). Clearly matches anchor 5; anchor 4 would require the 'when' clause to be less explicit than it is.

5 / 5

Trigger Term Quality

'PMF survey', 'measure product-market fit', '40% rule', 'Sean Ellis test', 'Rahul Vohra method', and 'how disappointed would you be' provide comprehensive natural-term coverage with multiple synonyms a user would actually say. Matches anchor 5; no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Triggers like 'Sean Ellis test' and 'Rahul Vohra method' occupy a clear niche with minimal overlap risk against generic survey or roadmap skills. Matches anchor 5; anchor 4's 'minor overlap risk with closely related skills' understates how distinctive these named triggers are.

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

saski/arnesto

Path

.agents/skills/pmf-survey/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.