Token导航 LogoToken导航TokenDH.com
待分类需要联网github未标认证来源可访问许可证需确认审计通过

lead-routing引导路由

Agent Skill

lead-routing 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

14,582

周安装

620

GitHub Stars

89

下载量

5,109
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:lead-routing(引导路由)
来源仓库:https://github.com/claude-office-skills/skills
仓库路径:skills/lead-routing
安装命令:
npx skills add https://github.com/claude-office-skills/skills --skill lead-routing
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/claude-office-skills/skills --skill lead-routing

简介

用于处理 GitHub 仓库、Issue 和 Pull Request 等协作信息。

  • 适用于围绕代码变更、仓库状态或协作事项进行整理和分析。
  • 可通过来源仓库和 README 进一步核验具体用法和功能边界。
  • 安装前建议确认权限范围及是否触发联网或文件读写操作。
  • lead-routing 属于待分类类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Lead Routing

Intelligent lead assignment and routing system with AI-powered scoring, territory mapping, round-robin distribution, and workload balancing. Based on n8n's HubSpot/Salesforce automation templates.

Overview

This skill covers:

  • Lead scoring and qualification
  • Territory-based routing
  • Round-robin distribution
  • Workload balancing
  • SLA monitoring and escalation

Routing Strategies

1. Rule-Based Routing

routing_rules:
  # By Company Size
  - name: "Enterprise Routing"
    condition:
      company_size: ">= 500"
      OR:
        annual_revenue: ">= $10M"
    assign_to: "Enterprise Team"
    priority: high
    sla: 1_hour

  - name: "Mid-Market Routing"
    condition:
      company_size: "100-499"
    assign_to: "Mid-Market Team"
    priority: medium
    sla: 4_hours

  - name: "SMB Routing"
    condition:
      company_size: "< 100"
    assign_to: "SMB Team"
    priority: standard
    sla: 24_hours

  # By Geography
  - name: "APAC Routing"
    condition:
      country: ["China", "Japan", "Singapore", "Australia"]
    assign_to: "APAC Team"
    timezone_aware: true

  - name: "EMEA Routing"
    condition:
      country: ["UK", "Germany", "France", "Netherlands"]
    assign_to: "EMEA Team"

  - name: "Americas Routing"
    condition:
      country: ["US", "Canada", "Brazil", "Mexico"]
    assign_to: "Americas Team"

  # By Industry
  - name: "Healthcare Specialist"
    condition:
      industry: ["Healthcare", "Pharmaceuticals", "Medical Devices"]
    assign_to: "Healthcare Sales"

  - name: "Finance Specialist"
    condition:
      industry: ["Banking", "Insurance", "FinTech"]
    assign_to: "Financial Services Sales"

2. Round-Robin Distribution

round_robin_config:
  team: "SMB Sales"
  members:
    - name: Alice
      capacity: 100%
      max_leads_per_day: 20

    - name: Bob
      capacity: 100%
      max_leads_per_day: 20

    - name: Carol
      capacity: 50%  # Part-time
      max_leads_per_day: 10

  rules:
    distribution: weighted  # or equal
    skip_if:
      - out_of_office: true
      - at_capacity: true
    reset: daily

  tracking:
    log_assignments: true
    balance_check: hourly

Distribution Algorithm:

┌─────────────────────────────────────────────────────────────┐
│                   ROUND-ROBIN LOGIC                         │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  1. New lead arrives                                        │
│                    │                                        │
│                    ▼                                        │
│  2. Check team availability                                 │
│     - Filter out: OOO, at capacity, off-hours              │
│                    │                                        │
│                    ▼                                        │
│  3. Calculate weighted position                             │
│     - Current assignments today                             │
│     - Capacity percentage                                   │
│     - Last assignment time                                  │
│                    │                                        │
│                    ▼                                        │
│  4. Assign to rep with lowest weighted score               │
│                    │                                        │
│                    ▼                                        │
│  5. Update tracking, notify rep                            │
│                                                             │
└─────────────────────────────────────────────────────────────┘

3. AI-Powered Lead Scoring

ai_scoring:
  provider: openai
  model: gpt-4

  input_factors:
    demographic:
      - company_size
      - industry
      - job_title
      - location

    firmographic:
      - annual_revenue
      - employee_count
      - funding_stage
      - tech_stack

    behavioral:
      - pages_visited
      - content_downloads
      - email_engagement
      - demo_requests

    fit_score:
      - icp_match_percentage
      - competitor_usage
      - budget_authority

  scoring_prompt: |
    Score this lead from 0-100 based on:

    Our ICP (Ideal Customer Profile):
    - B2B SaaS companies
    - 50-500 employees
    - Series A or later
    - Using {competitor} or {similar_tool}

    Lead Data:
    {lead_data}

    Return JSON:
    {
      "score": 0-100,
      "fit_score": 0-100,
      "intent_score": 0-100,
      "tier": "A/B/C/D",
      "reasoning": "...",
      "recommended_action": "...",
      "routing_suggestion": "..."
    }

  tier_thresholds:
    A: 80-100  # Hot lead, immediate follow-up
    B: 60-79   # Qualified, standard follow-up
    C: 40-59   # Nurture, marketing sequence
    D: 0-39    # Low priority, long-term nurture

4. Territory Mapping

territory_map:
  north_america:
    west:
      states: [CA, WA, OR, NV, AZ, CO, UT]
      owner: "West Coast Team"
      reps: [Alice, Bob]

    central:
      states: [TX, IL, OH, MI, MN, WI]
      owner: "Central Team"
      reps: [Carol, David]

    east:
      states: [NY, MA, PA, FL, GA, NC]
      owner: "East Coast Team"
      reps: [Eve, Frank]

  international:
    emea:
      countries: [UK, DE, FR, NL, ES, IT]
      owner: "EMEA Team"
      timezone: "Europe/London"

    apac:
      countries: [JP, SG, AU, KR, IN]
      owner: "APAC Team"
      timezone: "Asia/Tokyo"

  overlap_resolution:
    # When lead matches multiple territories
    priority_order:
      1: named_account_owner  # If account already has owner
      2: industry_specialist  # If industry requires specialist
      3: geography           # Default to geography

5. Workload Balancing

workload_balancer:
  check_frequency: hourly

  metrics_tracked:
    - current_open_leads
    - leads_assigned_today
    - leads_assigned_this_week
    - average_response_time
    - conversion_rate

  balance_rules:
    max_variance: 20%  # Max difference between reps

    rebalance_trigger:
      - variance > max_variance
      - rep_at_capacity
      - rep_underperforming

    rebalance_actions:
      - pause_assignments: for_overloaded_rep
      - increase_weight: for_underloaded_rep
      - notify_manager: when_rebalancing

  capacity_management:
    per_rep:
      max_open_leads: 50
      max_new_per_day: 15
      max_new_per_week: 60

    team_level:
      overflow_queue: true
      overflow_notify: sales_manager
      escalation_threshold: 2_hours

Workflow Implementation

Complete Lead Routing Workflow

workflow: "Intelligent Lead Router"

trigger:
  - type: hubspot_contact_created
  - type: form_submission
  - type: api_webhook

steps:
  1. enrich_lead:
      providers: [clearbit, zoominfo]
      fields:
        - company_size
        - industry
        - revenue
        - location
        - linkedin_url

  2. score_lead:
      method: ai_scoring
      store_result:
        hubspot_property: lead_score

  3. determine_tier:
      A_tier: score >= 80
      B_tier: score >= 60
      C_tier: score >= 40
      D_tier: score < 40

  4. apply_routing_rules:
      sequence:
        - check: named_account_owner
        - check: industry_specialist
        - check: territory_match
        - check: round_robin_availability

  5. assign_owner:
      hubspot:
        update_contact:
          hubspot_owner_id: "{selected_owner_id}"
          lead_status: "New"
          lead_tier: "{tier}"
          routing_reason: "{routing_logic}"

  6. create_task:
      hubspot:
        type: CALL
        subject: "Follow up: New {tier} lead - {company}"
        due_date: "{sla_deadline}"
        priority: "{priority_based_on_tier}"
        notes: |
          Lead Score: {score}
          Routing Reason: {routing_reason}
          Key Info: {summary}

  7. notify_owner:
      slack_dm:
        message: |
          🎯 *New Lead Assigned*

          **{contact_name}** at **{company}**
          Score: {score} ({tier} Tier)

          📞 SLA: Respond within {sla_time}

          Quick actions:
          • [View in HubSpot]({hubspot_link})
          • [LinkedIn]({linkedin_url})
          • [Schedule Call]({calendly_link})

  8. start_sla_timer:
      deadline: "{sla_deadline}"
      escalation_path:
        - 50%_elapsed: reminder_to_owner
        - 80%_elapsed: notify_manager
        - 100%_elapsed: reassign + alert

SLA Management

sla_tiers:
  tier_a:
    response_time: 1_hour
    escalation_path:
      - 30min: slack_reminder
      - 45min: manager_alert
      - 60min: auto_reassign

  tier_b:
    response_time: 4_hours
    escalation_path:
      - 2h: slack_reminder
      - 3h: manager_alert
      - 4h: auto_reassign

  tier_c:
    response_time: 24_hours
    escalation_path:
      - 12h: slack_reminder
      - 20h: manager_alert
      - 24h: move_to_queue

sla_reporting:
  metrics:
    - response_time_avg
    - response_time_p90
    - sla_compliance_rate
    - escalation_count

  report_frequency: weekly
  recipients: [sales_manager, ops_manager]

Reporting Dashboard

# Lead Routing Report - {Week}

## Distribution Summary
| Rep | Assigned | Responded | Avg Response | SLA Met |
|-----|----------|-----------|--------------|---------|
| Alice | 45 | 43 | 1.2h | 96% |
| Bob | 42 | 40 | 1.8h | 90% |
| Carol | 38 | 38 | 0.8h | 100% |
| **Total** | **125** | **121** | **1.3h** | **95%** |

## By Tier
| Tier | Count | Avg Score | Converted | Conv Rate |
|------|-------|-----------|-----------|-----------|
| A | 25 | 87 | 12 | 48% |
| B | 45 | 68 | 15 | 33% |
| C | 35 | 52 | 5 | 14% |
| D | 20 | 28 | 1 | 5% |

## Routing Breakdown
- By Territory: 60%
- By Industry: 25%
- Round Robin: 15%

## Issues
- 3 leads waited >SLA (reassigned)
- Alice at 95% capacity (monitor)
- No coverage for Healthcare vertical (gap)

## Recommendations
1. Hire Healthcare specialist
2. Increase Bob's training (response time)
3. Adjust A-tier threshold to 85 (too many false positives)

Output Example

Request: "Route this lead: John Smith, CTO at TechCorp (500 employees, SF, SaaS)"

Output:

# Lead Routing Decision

## Lead Profile
- **Name**: John Smith
- **Title**: CTO
- **Company**: TechCorp
- **Size**: 500 employees
- **Location**: San Francisco, CA
- **Industry**: SaaS

## AI Scoring

{ "score": 85, "fit_score": 90, "intent_score": 80, "tier": "A", "reasoning": "Strong ICP fit - CTO at 500-person SaaS company in our target market. High authority buyer.", "recommended_action": "Immediate outreach - high-value prospect" }


## Routing Decision

**Assigned to**: Alice Chen (Enterprise West)

**Routing Logic**:

1. ✅ Territory: San Francisco → West Coast
2. ✅ Company Size: 500 → Enterprise tier
3. ✅ Industry: SaaS → No specialist needed
4. ✅ Availability: Alice has capacity (18/20 today)

## Action Items Created

1. **Task**: Follow up call
  - Due: 1 hour (Tier A SLA)
  - Priority: High
2. **Slack Notification**: Sent to Alice
3. **SLA Timer**: Started (1h countdown)

## Recommended Outreach

Subject: Quick question about {pain_point} at TechCorp

Hi John,

Noticed TechCorp is scaling fast - congrats on the growth.

CTOs at similar SaaS companies often tell us {common_challenge}.

Would a 15-min call this week make sense to see if we can help?

[Calendly Link]


*Lead Routing Skill - Part of Claude Office Skills*

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude

33.59%
按下载量换算1,716

Codex

33.5%
按下载量换算1,712

Cursor

19%
按下载量换算971

Gemini CLI

9.35%
按下载量换算478

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills