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".
Install
With your agent
Install OMGSkills skill "zoominfo/zoominfo-mcp-plugin:skills/score-leads" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Zoominfo/zoominfo-mcp-plugin /tmp/zoominfo-mcp-plugin && ln -s /tmp/zoominfo-mcp-plugin/skills/score-leads ~/.claude/skills/score-leadsFrom README
Score Leads Tier leads as Hot / Warm / Cold with a response-time SLA tuned to the use case. Calls getgtmcontext(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 Tier and SLA are the first thing the rep sees — not buried under TL;DR or component breakdown. Resolution accuracy 100% — every input bucketed; email typos fail loudly, never silent fallback to name search. Every Hot lead carries verified contact data — phone + accuracy score visible. Bad data on a Hot lead = dial-the-wrong-number failure. Every tier comes with a concrete next action — "Direct dial 555-1234. Lead with [signal]." Not "engage promptly." Every lead carries a "why now" reasoning snippet — citing the specific axis driver (person seat × source × fresh trigger / intent / prior engagement).
More from this repo
account-health
Assess the health of an account from its recent conversations — sentiment trajectory and risk signals — backed by an...
account-relationship-recap
Recap where things stand with a company across recent conversations, with emphasis on how the relationship is evolving.
account-research
Produce a full intelligence brief on a target company — firmographics, CRM/account context, intent signals, recent...