Turn customer conversation notes, interview transcripts, call summaries, CRM snippets, or research notes into shared team learning and next questions.
SkillScore91Maintained
Automatic
◆Product Management pack
Last verified 8/15/2026
What it changes
Passed 20 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill91%
Checks it passed that the model alone missed
Categorizes Sarah Jenkins as Person.
Assigns Medium confidence level to this evidence.
Includes Segment as a column in the evidence table.
and 3 more in the full report
5 fixed15 passed either way2 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+1%
Agent turns
0%
Response time
-36%
Model gemini-3.6-flashMeasured 8/15/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
During our call with Acme Corp's IT Director, he mentioned: 'Our VP of Security, Sarah Jenkins, controls the $50k annual cloud security budget, but purchasing requires procurement approval from Legal.' Categorize Sarah Jenkins and the $50k budget into signal taxonomy labels.
What was checked, without and with the skill
Checked
Without skill
With skill
Categorizes Sarah Jenkins as Person.
Missed
Passed
Categorizes the $50k cloud security budget as Money.
Missed
Passed
case-08 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md85 linessingle file
Customer Learning Notes
Use this skill after customer conversations to turn raw notes into team-readable
evidence. Good notes make it harder to misremember, overfit, or let one founder
become the sole source of customer truth.
Source Traceability
Primary source: The Mom Test by Rob Fitzpatrick, especially chapter 8 and the
conclusion. Guidance is paraphrased for this MIT repo; authoring notes used
converted EPUB lines 3613-4445.
Signal Taxonomy
Use these labels when synthesizing notes:
Label
Meaning
Pain
Problem, obstacle, annoyance, risk, or cost
Goal
Desired outcome, job to be done, or priority
Workaround
Current manual process, tool stack, hack, or substitute
Money
Budget, cost, value, purchase process, or decision owner
Person
Specific stakeholder, competitor, team, buyer, or intro lead
Feature
Request, buying criterion, integration need, or implementation clue
Emotion
Strong excitement, anger, embarrassment, fear, or skepticism
Follow-up
Promise, task, intro, research item, or next step
Synthesis Workflow
Preserve concrete facts separately from interpretation.
Pull out short, useful quotes only when they are needed for traceability,
positioning, or internal alignment.
Tag signals using the taxonomy above.
Group evidence by segment, problem, workaround, budget, and commitment.
Identify contradictions and mixed-segment noise.
Update beliefs, risks, and the next three questions.
Recommend whether to continue, narrow the segment, ask for commitments, or
move to building/testing.