lead-scoring-model

$npx mdskill add OneWave-AI/claude-skills/lead-scoring-model

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.

SKILL.md

.github/skills/lead-scoring-modelView on GitHub ↗
---
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.

More from OneWave-AI/claude-skills

SkillDescription
accessibility-auditorAudit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
agent-armyDeploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
agent-swarm-deployerDeploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
agent-team-builderDesigns and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
agent-to-agentAgent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
ai-readiness-assessmentAssesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
animateGenerate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
api-documentation-writerGenerate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.
api-endpoint-scaffolderGenerate REST API endpoints with proper structure, validation, error handling, and types. Use when creating new API routes, endpoints, or backend services.
api-load-testerLoad tests API endpoints with progressive concurrency. Measures response times, error rates, throughput, and identifies breaking points. Generates a detailed report with latency percentiles, throughput curves, bottleneck analysis, and optimization recommendations.