lead-triage

作者: anthropic

根據參與信號、公司契合度及緊急標記對HubSpot的入庫潛在客戶進行評分,生成「今日優先致電這5位」清單,附帶談話要點,並草擬…

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill lead-triage

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_statusUnqualified. Use the field list in reference/hubspot-scoring.md. If HubSpot is unavailable, stop: "HubSpot is disconnected — connect it and try again."

  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:

    • 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)
  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, matching the tone of their last outbound thread in Mail. Show draft; do not send.

  6. 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

來自 anthropic 的更多技能

access
anthropic
管理 Discord 頻道存取權限 — 核准配對、編輯允許清單、設定私訊/群組政策。當使用者要求配對、核准某人、查詢誰被允許時使用…
official
session-report
anthropic
從 ~/.claude/projects 的對話記錄中,生成一份可探索的 HTML 報告,內容涵蓋 Claude Code 工作階段的使用情況(包含 token、快取、子代理、技能及高成本提示)。
official
build-mcp-server
anthropic
當使用者要求「建立 MCP 伺服器」、「建立 MCP」、「製作 MCP 整合」、「為 Claude 包裝 API」、「暴露工具給…」時,應使用此技能。
official
cookbook-audit
anthropic
根據評分標準審核 Anthropic Cookbook 筆記本。每當要求進行筆記本審查或審核時使用。
official
handle-complaint
anthropic
處理進線客戶投訴的完整流程——提取背景資訊、草擬回覆,並建議營運改善方案。可接受選填的電子郵件或工單編號……
official
use-case-triage
anthropic
快速判斷某項處理活動是否需要PIA、強制性的GDPR DPIA,或可直接進行——揭露隱私政策衝突,並引導至正確的…
official
board-minutes
anthropic
根據您指定的格式,自動草擬董事會或委員會會議記錄。自動從您的日曆中偵測即將召開的董事會及委員會會議,詢問議程及…
official
renewal-tracker
anthropic
顯示即將到來的取消截止日期的合約,並在通知窗口關閉前發出警告,依據維護中的續約登記表進行操作。當用戶詢問時使用…
official