lead-triage
GitHub基于HubSpot数据对线索进行评分，生成优先联系列表及话术。支持起草跟进邮件和提议会议时间，但需人工审批后才发送或预订。适用于线索优先级排序、确定首拨对象及管道管理场景。
Trigger Scenarios
Install
npx skills add anthropics/knowledge-work-plugins --skill lead-triage -g -y
SKILL.md
Frontmatter
{
"name": "lead-triage",
"version": "0.1.1",
"description": "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."
}
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=LeadorMQLandhs_lead_status≠Unqualified. 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
CustomerorEvangelistlifecycle 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
Version History
- 6f13415 Current 2026-07-05 18:35
