Skip to main content
skill CX Codex official · Anthropic

lead-triage · anthropics, small-business — Claude Code skill for lead scoring

The lead-triage Claude Code skill scores and ranks inbound HubSpot leads by engagement, company fit, and urgency. It activates when asked to prioritize leads or decide who to call first.

Apache-2.0 ★ 36,654 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install small-business@knowledge-work-plugins
Open on GitHub

What lead-triage does

The skill fetches HubSpot contacts and scores each one for engagement, company fit, urgency, and recency. It returns a ranked list with scores, call talking points, and a summary of recent activity. When scores are too close to support a ranking, it sorts by CRM facts instead.

It can also draft follow-up emails and suggest call times. Emails are never sent, and calendar events are never created without the owner’s approval. If HubSpot is unavailable, provide a CSV export or paste a contact list; connected Apollo or Clay can enrich lead data, with credit use subject to approval.

What it helps with

  • prioritize inbound leads
  • choose which lead to call first
  • prepare talking points for lead calls
  • draft follow-up emails for selected leads
  • suggest call times for high-priority leads

Example prompts for the agent

  • Score my inbound leads and list who to call first.
  • Rank the HubSpot leads by urgency and prepare call talking points.
  • Draft follow-up emails for these leads and suggest call times.

How to install lead-triage

1Plugin marketplace

/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install small-business@knowledge-work-plugins

This installs the whole small-business plugin with all its skills

2Skills CLI (Vercel)

npx skills add anthropics/knowledge-work-plugins --skill lead-triage -a claude-code

3Manually: put the files in place

~/.claude/skills/lead-triage/SKILL.md

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

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

Questions about lead-triage

How do I install lead-triage in Claude Code?

Run /plugin marketplace add anthropics/knowledge-work-plugins, then run /plugin install small-business@knowledge-work-plugins.

What does lead-triage do?

It scores HubSpot leads using engagement, company fit, urgency, and activity recency, then returns a prioritized list with call talking points. It can also draft follow-ups and suggest call times.

What does lead-triage need to work?

Use a connected HubSpot account, or provide a CSV export or pasted contact list. Apollo or Clay is only needed for data enrichment, and credit use requires the owner’s approval.

Source text

SKILL.md · Apache-2.0
---
name: lead-triage
version: 0.1.1
description: >
  Scores inbound HubSpot leads by engagement signals, company fit, and urgency
  markers, ranks the ones worth a call today with talking points, drafts the
  follow-ups, and proposes calendar times for the owner to book. Use when the
  owner asks to prioritize, score, or rank leads, asks "who should I call
  first," or asks about their pipeline. An ask that wants the ranked leads
  turned into a call list with time blocked on the calendar routes to
  /call-list, which runs this skill first and then books the time.
allowed-tools: Read, WebFetch
---

# Lead Triage

## Quick start

Pull inbound leads from HubSpot, score them, and surface a ranked call list with talking points. Drafts follow-ups and proposes calendar slots — never sends or books without owner approval.

```
User: "prioritize my leads"
→ Pull contacts: lifecycle stage Lead or MQL, status ≠ Unqualified
→ Score each across engagement, company fit, urgency, recency
→ Return ranked list (size adapts to volume) with talking points
→ Offer to draft follow-ups and propose calendar slots
```

## Workflow

1. **Pull leads from HubSpot.** Fetch contacts with `lifecyclestage` = `Lead` or `MQL` and `hs_lead_status` ≠ `Unqualified`. Use the field list in [reference/hubspot-scoring.md](reference/hubspot-scoring.md). If HubSpot is unavailable — not installed, not connected, or erroring — do not stop. Say so plainly and run the "No HubSpot?" path at the bottom of this file: ask for a CSV export or a rough pasted list, and score that instead.
   - **Empty portal check.** If the pull returns zero contacts of any lifecycle stage, the portal is empty, not filtered wrong. Say so in one line, offer HubSpot's own setup (`manage_onboarding`, action `SET_GOAL`) or the "No HubSpot?" path, and do not diagnose lifecycle stages on a portal with nothing in it. The count is the test: `get_user_details` returns an `onboarded` flag, but a portal can report `onboarded: false` while holding hundreds of contacts, so the flag alone never decides this.

2. **Clarify if trigger is ambiguous.** If the user said only "pipeline" without a qualifier, ask: *"Quick pipeline overview (deal stages + total value) or prioritized call list?"* — then route accordingly. Do not score leads on a bare "pipeline."

3. **Score each lead.** Apply the four-dimension model in [reference/hubspot-scoring.md](reference/hubspot-scoring.md):
   - **Engagement** — email replies, opens, site visits in HubSpot (last 30 days only)
   - **Company fit** — industry and employee count vs. owner's ICP (default: any industry, 1–50 employees). Read these from the company associated with the lead, not from the contact record — see the scoring reference. When leads have no associated company and a lead-data connector (Apollo or Clay) is connected, the enrichment leg in the scoring reference fills industry and size from the lead's email domain. It is metered — say how many rows it would enrich and what that costs in credits, and run it only on the owner's yes for this run. Nothing enriched is written back to the CRM from here.
   - **Urgency** — lead age, stage duration, notes containing "urgent / ASAP / deadline / budget approved". The keyword check requires actually fetching note bodies via the contact → notes association — follow the "Fetch note bodies" section of the scoring reference; the note count alone cannot fire it.
   - **Recency penalty** — subtract points if last activity was <24 hours ago (already touched today)

   **Then check whether the scores actually separated.** If the highest and lowest composite differ by less than 10 points, the CRM has no signal to rank on. Do not present the order as a ranking — run the flat-score path in the scoring reference, say plainly that the signals are empty, and order by CRM facts instead. A false ranking sends the owner to call the wrong person.

4. **Build the ranked list.** Sort descending by composite score. Adapt list size to volume:
   - ≤10 leads → show all
   - 11–30 leads → show top 5
   - >30 leads → show top 8

   For each lead: name, company, score, one-paragraph talking point, last activity summary. If engagement signals are all >30 days old, flag: *"Engagement signals are stale — approach as cold outreach."*

5. **Offer follow-up drafts.** Ask: *"Draft follow-ups for any of these?"* If yes, write one email per selected lead in the owner's voice per [the shared voice profile](../../shared/voice-profile.md). If that file has no profile yet, follow its "When there is no sample" instruction — ask for three emails the owner was happy with; if they decline, draft plain and neutral and say the drafts are un-voiced. Never invent a personality. Show drafts; do not send. If Mail is unavailable, hand the drafts over in chat as subject plus body for the owner to paste — that is a complete outcome.

6. **Render the triage board as an artifact.** After the short chat answer — never instead of it — build an HTML page using the house artifact style (`../../shared/artifact-style.md`): a ranked table with each lead's composite score in mono, an urgency status pill per row (good / warn / critical), and a talking-points line under each lead. If the flat-score path fired, say so on the page and drop the pill colors to neutral.

7. **Offer calendar slots.** Ask: *"Propose call slots for any of these?"* If yes, check Calendar for open 30-minute windows in the next two business days (avoid slots with existing events ±15 min). Propose two options per lead. Never create calendar events without explicit owner approval. If Calendar is unavailable, ask the owner for two or three windows they can offer and use those instead of inventing times.

## Approval gates

- **Never send an email.** Draft only; owner sends from their inbox.
- **Never create calendar events until approved by the user.**
- **Never change lifecycle stage or mark a lead Unqualified** unless the owner explicitly asks.
- **Never include `Customer` or `Evangelist` lifecycle contacts** in the lead list.
- **If zero leads match the filter**, explain why and offer to check what lifecycle stages are in use — do not fabricate a list.

## Reference

- [reference/hubspot-scoring.md](reference/hubspot-scoring.md) — HubSpot field names, scoring weights, ICP defaults
- [reference/gotchas.md](reference/gotchas.md) — edge cases: stale data, zero leads, pipeline disambiguation, customer contamination
- [reference/examples/happy-path-triage.md](reference/examples/happy-path-triage.md) — worked output for a 7-lead list with draft and slot proposal

## Closing offer

End with one line on what the triage produced, then the most relevant next step with its trigger phrase — usually "call list" (`/call-list`) to add calendar blocks around the ranking. Up to two others when they fit: "write this outreach" (`outreach-composer`) or "update the CRM" (`crm-autopilot`). Never more than three, and never re-offer something the owner already declined this session.

## No HubSpot?

Paste or upload the lead list — a CSV export or even a rough list works. Scoring and talking points run the same; the ranked call list comes back as chat plus a file instead of writing to the CRM.

## Using a tool that isn't listed

The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.

© Anthropic · Apache-2.0 · anthropics/knowledge-work-plugins

Similar skills

All skills for Marketing and content →

lead-triage by other authors comes first.

lead-triage official anthropics lead-triage scores inbound leads against ICP criteria, ranks lead backlogs, and suggests the next action. Works with connected CRMs or plain pasted tables. CX Codex +1 1,800installs lead-triage ilyautov lead-triage scores incoming CRM leads by engagement, ICP fit and urgency, then returns a ranked who-to-call-today list with talking points. Triggers on prompts like "triage the leads" or "who do I call first". CX Codex +1 ★ 38repo stars build-lead-scoring tomgranot build-lead-scoring — a Claude Code skill that builds a HubSpot lead scoring model with separate Fit and Engagement scores. Replaces the retired HubSpot Score property. CX Codex +1 ★ 81repo stars suede-revops JasonColapietro suede-revops drafts lifecycle, lead-scoring, and routing rules for revenue operations. Use it to plan CRM processes and marketing-to-sales handoffs. CX Codex +1 ★ 121repo stars lifecycle-progression-workflow tomgranot lifecycle-progression-workflow — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. It builds four HubSpot workflows that move contacts from Lead to Customer when specific events fire. CX Codex +1 ★ 81repo stars lead-qualification Cogny AI The lead-qualification skill for Claude Code researches a prospect against your ideal customer profile, reviews company details and suggests a next step for one lead or a list. CX Codex +1 ★ 116repo stars inbound-lead-qualifier OneWave-AI inbound-lead-qualifier — a skill for Claude Code, Codex, Cursor, and five other platforms that scores inbound leads against ICP fit, intent and urgency, then routes them to the right sales rep with a call script and qualification questions. CX Codex +1 343installs lead-scoring-model OneWave-AI 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. CX Codex +1 253installs

From the same set263

The whole set →
deal-advance-gap deal-advance-gap finds missing requirements to advance a deal to the next stage or close. Spots blockers and outlines who needs to do what by when. CX Codex +1 374installs deal-slip-scenario deal-slip-scenario simulates the forecast impact when a deal slips, shrinks, or is lost. Calculates quota gaps and the substitute pipeline needed to stay on track. CX Codex +1 372installs update-opportunity Update opportunity fields in a CRM, then review the changes before they’re written. Useful for moving a deal to a new stage or revising its close date, amount, next step, or forecast category. CX Codex +1 371installs setup setup is a Claude Code skill that checks connected tools, learns your writing style from sent email, and builds a starter dashboard without a questionnaire. For first run. CX Codex +1 371installs weekly-wrap The weekly-wrap skill for Claude Code generates an end-of-week summary of pipeline movement and sets up tasks for Monday. It activates when users ask for a weekly wrap-up or a Friday summary. CX Codex +1 ★ 36,654repo stars team-pipeline The team-pipeline Claude Code skill rolls up a team’s pipeline by rep and stage. Ask for a team forecast, pipeline review prep, or areas where reps need coaching. CX Codex +1 ★ 36,654repo stars stakeholder-map stakeholder-map is a Claude Code skill that maps deal and account stakeholders, roles, and influence paths. It runs when analyzing account relationships. CX Codex +1 ★ 36,654repo stars route-lead The route-lead Claude Code skill assigns owners to leads and opportunities using an organization’s rules. It runs on requests to assign a lead or process the routing queue. CX Codex +1 ★ 36,654repo stars

Project sponsors

Companies that keep this analytics open