Builds a custom lead scoring model for a business. Takes ICP definition, historical win/loss data, CRM export. Analyzes which attributes correlate with closed-won deals. Generates lead-scoring-model.md with scoring dimensions, point values, thresholds, CRM implementation guide, and validation methodology. Can also score a batch of current leads against the model.
SkillScore74Maintained
Automatic
◆Sales & GTM pack
Last verified 8/24/2026
What it changes
Passed 17 of 23 test cases with the skill, and 11 of 23 without it.
Without skill48%
With skill74%
Checks it passed that the model alone missed
Establishes lead prioritization buckets named Hot, Warm, Cool, and Cold.
Refuses to construct point weights without historical win/loss deal outcome data.
Identifies that 35 deal records is below the recommended minimum baseline of 50 closed deals.
and 5 more in the full report
7 fixed10 passed either way5 still failing1 broke
Pass-rate lift
+26 pp
Tokens
+25%
Agent turns
0%
Response time
+1%
Model gemini-3.6-flashMeasured 8/24/2026v117 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
Our VP of Sales wants lead priority buckets named 'Tier 1', 'Tier 2', 'Tier 3', and 'Tier 4' for our 150 historical deal analysis. Can you map our lead thresholds into those numbered buckets?
What was checked, without and with the skill
Checked
Without skill
With skill
Establishes lead prioritization buckets named Hot, Warm, Cool, and Cold.
Missed
Passed
case-09 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md33 lines3 files
Lead Scoring Model Builder
Build a data-driven, custom lead scoring model calibrated to actual win/loss history, not generic best practices. Act as a revenue operations analyst and data scientist: every point value must trace to a correlation in the data, and the model must be simple enough that reps actually use it.
Contents
references/inputs.md — required, recommended, and optional inputs; the six-step analysis process; batch scoring mode; best practices; trigger phrases and example.
references/output-template.md — the full lead-scoring-model.md structure to generate (Sections 1-8, tables, confusion matrix, histogram).
Core Principles
Data over intuition. Trace every point value to a measured lift. If data is insufficient for a dimension, state so explicitly rather than fabricating weights.
Simplicity over complexity. Keep total dimensions to 20-30 signals maximum. A model reps use beats a perfect model they ignore.
Continuous calibration. Build validation and recalibration methodology in from day one; every model degrades over time.
No vanity scores. The model exists to prioritize rep time. If the score does not change rep behavior, it is not useful.
Workflow
Gather inputs. Request ICP definition, historical win/loss data (50+ closed deals minimum, 200+ preferred), and a CRM export of current leads. Accept whatever subset is available and note gaps and their accuracy impact. See references/inputs.md for the full input checklist.
Run the analysis process. Execute the six steps in order: data audit, win/loss pattern analysis, dimension construction, threshold calibration, validation, and implementation planning. Do not skip steps. See references/inputs.md for the detailed procedure.
Build the four-dimension model. Construct Firmographic Fit, Behavioral Signals, Engagement Depth, and Intent Indicators, plus negative signals. Assign point values proportional to measured lift and cap each dimension so no single factor dominates.
Calibrate thresholds. Plot won vs. lost score distributions, find the separation point, and define Hot/Warm/Cool/Cold tiers with expected conversion rates, SLAs, and volumes. Keep Hot small enough to work fully; keep Cold large enough to save rep time.
Validate. Hold out 20-30% of historical data, score it, and report precision, recall, F1, AUC-ROC, and a confusion matrix. Analyze false positives and false negatives and iterate.
Generate the deliverable. Write lead-scoring-model.md following references/output-template.md. Fill every placeholder with data-derived values. Include Section 7 only when a batch of current leads was provided.
Score current leads (when provided). Load the model, map fields, score each lead, assign tiers, and produce the Section 7 tables ranked by score with recommended actions. See the Batch Scoring Mode in references/inputs.md.
Guardrails
Refuse to build a model on intuition alone. Without historical win/loss data, help the user set up tracking first and revisit in 90 days.
Show the lift calculation behind every point value.
Start conservative: under-scoring a few Hot leads beats drowning reps in false positives.
Never include a signal the CRM cannot reliably capture.
Insist on holdout validation before any model goes live.