CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mom-test

Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", or "interview script". Also trigger when preparing user research questions, interpreting ambiguous customer feedback, or designing customer discovery processes that avoid false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.

Quality

91%

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

78%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, highly actionable framework skill with excellent progressive disclosure into a verified bundle of reference files. Its main weaknesses are token efficiency — an irrelevant author bio, affiliate link, known-psychology explanations, and duplicated reference links — and a workflow presented as parallel framework sections rather than an explicitly sequenced process.

Suggestions

Remove the "About the Author" section and the affiliate-tagged Amazon link; neither affects task execution and they pad the token budget. Also deduplicate the per-section "See:" links against the consolidated Reference Files list, keeping one of the two.

Trim the "Why it works" paragraphs to one line each or fold them into "Core concept"; several restate behavioral psychology Claude already knows (e.g., people are unreliable predictors of future behavior, memory is biased).

Add an explicit end-to-end sequence (e.g., 1. Define your ask → 2. Recruit casually → 3. Run the conversation with copy patterns → 4. Score 0-10 → 5. Process notes and update beliefs) so the lifecycle order of the sections becomes an operational workflow rather than an implicit one.

DimensionReasoningScore

Conciseness

The core framework content (rules, good/bad questions, copy patterns, tables) is dense and skill-specific, but there is noticeable padding: an "About the Author" biography and an Amazon affiliate link irrelevant to task execution, "Why it works" paragraphs restating psychology Claude already knows ("Humans are terrible at predicting their own behavior", "Memory is unreliable and biased"), insights repeated across sections (the "would you buy this" trap appears in sections 2, 3, and Common Mistakes), and reference links duplicated both at the end of every section and again in the Reference Files list. This fits the mostly-efficient-but-could-be-tightened anchor rather than the score-2 anchor, since the padding is localized and the bulk earns its tokens.

3 / 5

Actionability

For an instruction-only skill, the guidance is fully executable: copy-paste-ready question scripts ("Tell me about the last time you...", "What's the next step here?"), concrete good/bad question contrasts, per-context example tables covering common cases (idea validation, pricing, B2B, pre-launch), and an operational scoring rubric ("rate them 0-10... Always provide the current score and specific improvements needed to reach 10/10"). This matches the top anchor of copy-paste-ready guidance with examples covering the common cases; score 4 would require minor gaps, and none are evident.

5 / 5

Workflow Clarity

The six sections follow the conversation lifecycle in a sensible order (rules → question quality → deflecting bad data → commitment → finding conversations → processing), and the Quick Diagnostic table provides explicit checkpoints with remediation ("Did they give you a commitment? ... If No: Ask for a specific next step"), reinforced by the 10/10 scoring feedback loop. It falls short of the top anchor because the lifecycle sequence is implicit rather than presented as an explicit numbered workflow with pre/during/post-conversation phases, and preparation steps (e.g., "know your ask before the meeting") are embedded in section prose rather than sequenced.

4 / 5

Progressive Disclosure

The body is a well-organized overview with each section ending in a clearly signaled one-level-deep pointer ("See: [references/question-patterns.md]"), a consolidated Reference Files list with per-file descriptions, and all six bundle files verified to exist at the referenced paths. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation; the only nit — case-studies.md appearing only in the consolidated list rather than inline — is too minor for score 4's "organization gaps".

5 / 5

Total

17

/

20

Passed

Description

100%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 exemplary description: third-person, concrete about capabilities, with an explicit and richly enumerated trigger clause covering natural user phrasings, and explicit disambiguation pointers to neighboring skills. All four dimensions sit at the top anchor with no over-claiming or padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: "discuss their life not your idea, ask about specifics in the past, and talk less", plus "commitment and advancement, avoiding compliments, and extracting signal from noise" — comprehensive coverage of the framework's capabilities, not vague language. It stays in third person ("Talk to customers"), matching the anchor for listing multiple specific concrete actions with comprehensive coverage; score 4 would require minor coverage gaps, which are absent.

5 / 5

Completeness

It explicitly answers both questions: what ("Talk to customers without leading them using Mom Test rules..." with the rules enumerated) and when ("Use when the user mentions..." followed by concrete trigger phrases, plus "Also trigger when preparing user research questions..."). This matches the anchor for clearly and explicitly answering both what AND when with concrete trigger phrases; score 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It includes many natural phrases users would actually say: "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", "interview script", plus secondary triggers like "preparing user research questions" and "interpreting ambiguous customer feedback". Coverage includes synonyms and colloquial phrasings (file extensions are not applicable to this non-file skill), matching the comprehensive-coverage anchor; score 4 would mean a few natural terms are missing, and none are apparent.

5 / 5

Distinctiveness Conflict Risk

The niche is distinct (customer-interview methodology under The Mom Test) with unambiguous triggers, and it actively reduces overlap risk by routing adjacent intents elsewhere: "For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint." This matches the clear-niche/minimal-conflict anchor; score 4 would require minor overlap risk with closely related skills, and the explicit routing addresses exactly that.

5 / 5

Total

20

/

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

valeriibeck-star/claude-skills

Path

skills/mom-test/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.