ClaudeSuperPower
SubmitLog in

score-leads

Skill

Score and prioritize leads or cold contacts (mixed ZoomInfo person IDs, emails, or name+company rows). Returns Hot / Warm / Cold tier per lead with a response-time SLA tuned to the use case (live inbound routing, MQL triage, event follow-up, PQL triage, content follow-up, SDR queue ordering), per-ax

0Backend

Install

git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git ~/.claude/skills/score-leads

What is score-leads?

Score and prioritize leads or cold contacts (mixed ZoomInfo person IDs, emails, or name+company rows). Returns Hot / Warm / Cold tier per lead with a response-time SLA tuned to the use case (live inbound routing, MQL triage, event follow-up, PQL triage, content follow-up, SDR queue ordering), per-axis breakdown (person fit · account fit · source signal · trigger), a "why now" reasoning snippet per lead, and recommended next action with verified contact data. Resolution by email is deterministic; name+company surfaces verification when needed; typo'd emails fail explicitly rather than fall back. Iteratively refinable. Triggers on phrases like "score these leads", "which lead/contact should I call first", "prioritize my MQLs", "rank inbound", "who should I prioritize?", "tier this list".

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~199 tokens of context used while enabled, before you invoke anything

Documentation

README · ~12 min read

Score Leads

Tier leads as Hot / Warm / Cold with a response-time SLA tuned to the use case. Calls get_gtm_context(detailed: true) unconditionally, resolves leads by email (deterministic) or name+company (surface ambiguity), scores on four axes, and presents a scannable per-lead output with a specific "why now" reasoning snippet so the rep can trust the tier.

The bar

  1. Tier and SLA are the first thing the rep sees — not buried under TL;DR or component breakdown.
  2. Resolution accuracy 100% — every input bucketed; email typos fail loudly, never silent fallback to name search.
  3. Every Hot lead carries verified contact data — phone + accuracy score visible. Bad data on a Hot lead = dial-the-wrong-number failure.
  4. Every tier comes with a concrete next action — "Direct dial 555-1234. Lead with [signal]." Not "engage promptly."
  5. Every lead carries a "why now" reasoning snippet — citing the specific axis driver (person seat × source × fresh trigger / intent / prior engagement). Never the composite restated; never generic ("strong fit"). Same trust discipline as score-accounts.
  6. Output scannable in <30 seconds per row. Component breakdown below the fold.

Scope

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.