mcpbeat Sign in

Lead Triage Skill for Claude

> Scores inbound HubSpot leads by engagement signals, company fit, and urgency markers to produce a "call these 5 today" list with talking points, drafts the follow-ups, and blocks Calendar time. Use when the user asks to prioritize leads, who to call first, or about their pipeline.

2k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
23273
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill lead-triage

What comes with it

6 079 bytes besides the instruction
reference/examples/happy-path-triage.md
reference/gotchas.md
reference/hubspot-scoring.md

The instruction itself

5 sections, as written by the author

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

  • Pull leads from HubSpot. Fetch contacts with lifecyclestage = Lead or MQL and hs_lead_statusUnqualified. Use the field list in reference/hubspot-scoring.md. If HubSpot is unavailable, stop: *"HubSpot is disconnected — connect it and try again."*
  • 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."
  • Score each lead. Apply the four-dimension model in 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)
  • Urgency — lead age, stage duration, notes containing "urgent / ASAP / deadline / budget approved"
  • Recency penalty — subtract points if last activity was <24 hours ago (already touched today)
  • 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."*

  • Offer follow-up drafts. Ask: *"Draft follow-ups for any of these?"* If yes, write one email per selected lead, matching the tone of their last outbound thread in Mail. Show draft; do not send.
  • 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. Do not create events — the owner books.

Approval gates

  • Never send an email. Draft only; owner sends from their inbox.
  • Never create calendar events. Propose times; owner books.
  • 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 — HubSpot field names, scoring weights, ICP defaults
  • reference/gotchas.md — edge cases: stale data, zero leads, pipeline disambiguation, customer contamination
  • reference/examples/happy-path-triage.md — worked output for a 7-lead list with draft and slot proposal

Other skills for the same job

different authors, same section of the catalogue
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens
Workflow Automation
by ComeOnOliver
×3

Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility

3k tokens

How to use it

Copy the folder

Take anthropics/lead-triage from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.