Skip to main content
skill CX Codex

lead-scoring-model — Claude Code skill: data-driven lead scoring

This skill analyzes your sales history and builds a lead-scoring model tied to your actual deal data. It generates documentation with scoring dimensions, thresholds, and a CRM implementation guide.

MIT 253 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill lead-scoring-model -a claude-code
Open on GitHub

What lead-scoring-model does

The skill acts as a revenue operations analyst: it takes your ideal customer profile, win/loss history (minimum 50 deals, preferably 200+), and a CRM export. It identifies which attributes correlate with closed deals and assigns point values based on measured lift, not generic best practices.

Output is a lead-scoring-model.md with four dimensions (Firmographic Fit, Behavioral Signals, Engagement Depth, Intent Indicators), score tables, Hot/Warm/Cool/Cold tier thresholds with expected conversion rates, and implementation instructions. Includes holdout validation with precision, recall, and a confusion matrix.

If you provide current leads, the skill scores them against the model, assigns tiers, and returns ranked tables with prioritization recommendations. Relies on file reading, data analysis, and web search tools.

What it helps with

  • build a lead-scoring model from actual sales history
  • identify which customer attributes predict deal closure
  • set scoring thresholds and tiers for sales team prioritization
  • score current pipeline leads and rank them by conversion potential
  • validate the model and monitor performance over time

Example prompts for the agent

  • Build a lead-scoring model from deal history in deals.csv, ICP in icp.md, and current leads in crm_export.xlsx.
  • Analyze closed-won and closed-lost deals in sales_history.json and construct a 20+ dimension scoring model.
  • Score the leads in pipeline.csv against the existing model in lead-scoring-model.md and return a ranked tier table.

How to install lead-scoring-model

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill lead-scoring-model -a claude-code

2Manually: put the files in place

~/.claude/skills/lead-scoring-model/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/lead-scoring-model/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about lead-scoring-model

How do I install lead-scoring-model in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill lead-scoring-model -a claude-code, then check ~/.claude/skills/lead-scoring-model/SKILL.md. Installation commands differ for other platforms (Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode).

What does lead-scoring-model do?

It analyzes your company's win/loss history to determine which attributes correlate with closed deals, then builds a model that ranks your current leads by conversion probability. Every point value traces back to your data, not generic advice.

What if I don't have enough historical data?

You need at least 50 closed deals (wins and losses); 200+ is better. If you have less, the skill can help you set up tracking and revisit in 90 days. It also flags data gaps and their impact on model accuracy.

Source text

SKILL.md · MIT
---
name: lead-scoring-model
description: 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.
tools: Read, Write, Glob, Grep, Bash, WebSearch, WebFetch
---

# 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

1. **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.
2. **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.
3. **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.
4. **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.
5. **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.
6. **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.
7. **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.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Marketing and content →

From the same set185

The whole set →
deal-closer-playbook deal-closer-playbook analyzes in-flight B2B deals, runs web research on target accounts, and drafts an actionable deal-playbook.md document. CX Codex +1 256installs meeting-to-tasks meeting-to-tasks parses meeting transcripts into structured action items with assignees and deadlines, catches implicit commitments, and exports tasks for issue trackers. CX Codex +1 255installs overnight-repo-auditor overnight-repo-auditor runs an autonomous overnight code audit covering security, performance, accessibility, and dependencies without prompting for confirmation. CX Codex +1 253installs cowork-deal-room The cowork-deal-room skill reviews deal-room files in five stages and produces risk findings, term comparisons, and negotiation guidance. CX Codex +1 253installs incident-responder The incident-responder skill investigates production incidents by checking logs and recent changes, classifying severity, and preparing recovery guidance and a report. Use it during an outage and for follow-up. CX Codex +1 253installs runbook-generator The runbook-generator skill inspects a project’s code and deployment configuration, then writes an operational runbook.md. Use it to document releases, incident response, or disaster recovery. CX Codex +1 252installs data-pipeline-builder data-pipeline-builder turns source, destination and transformation notes into a runnable ETL/ELT pipeline: Python or SQL code, an Airflow DAG, quality checks and a spec file. CX Codex +1 252installs roi-calculator roi-calculator turns your current costs, manual hours and hourly rates into a written ROI report on an AI project, with payback and sensitivity cases. CX Codex +1 252installs

Project sponsors

Companies that keep this analytics open