Skill

lead-routing

Document or refine lead routing rules and criteria. Who gets which leads, when, and why. Trigger with "document lead routing", "lead routing rules for [team/segment]", or use the /document-lead-routing command.

Install

npx claudepluginhub propane-ai/kits --plugin kit-gtm

Tool Access

This skill uses the workspace's default tool permissions.

Preview

> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.1k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

claude-code-plugin-release

1 file

Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.

claude-mem

64.7k

Stats

Parent Repo Stars2

Parent Repo Forks1

Last CommitFeb 3, 2026

Actions

View Source View Plugin View on GitHub View README

If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.

Lead Routing

Document or refine lead routing rules and criteria: who gets which leads, when, and why. Use for RevOps, onboarding, and process documentation. This skill works with user input; when ~~CRM~~ or ~~project tracker~~ is connected, it can reference existing routing logic or tickets.

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                     LEAD ROUTING                                 │
├─────────────────────────────────────────────────────────────────┤
│  ALWAYS (works standalone)                                       │
│  ✓ Gather: segments, criteria, owners, round-robin vs. assignment │
│  ✓ Structure: rules table (criteria → owner/queue), exceptions   │
│  ✓ Output: routing doc with rules, SLA, escalation                │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + ~~CRM~~: Existing assignment rules, queues, ownership             │
│  + ~~project tracker~~: Routing tickets, process docs               │
└─────────────────────────────────────────────────────────────────┘

Output Structure

Rules table: Criteria (segment, source, score, region), Owner/queue, Priority.
Exceptions: Special cases, override rules.
SLA: Response time, handoff time.
Escalation: When and to whom to escalate.

Data Sources (per REFERENCE.md)

~~CRM~~ (if connected): Assignment rules, queues, ownership, lead source/score.
~~project tracker~~ (if connected): Process docs, routing tickets.
User input: Segments, criteria, owners, round-robin vs. assignment.