Command
analyze-distribution
Analyzes a Chili Piper distribution (round-robin queue) for imbalance vs. configured weights, booking-source and day-of-week skew, and cancellation breakdown.
@chili-piperView CommandAutomation
Command
/debug-distro
Debugs why a CRM record was routed (or not routed) through a Chili Piper distribution — explains each rule stage and recommends a targeted fix.
Install
> /plugin marketplace add Chili-Piper/mcp-assets > /plugin install chili-piper-skills@chili-piper-skills
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/debug-distro
Context preview
What this command does when you run it.
Debugs why a CRM record was routed (or not routed) through a Chili Piper distribution — explains each rule stage and recommends a targeted fix.
Command definition
debug-distro.mddescription: Debugs why a CRM record was routed (or not routed) through a Chili Piper distribution — explains each rule stage and recommends a targeted fix.
argument-hint: "<log-id|salesforce-id|record-name> [router-id] [workspace] [date-range]"
allowed-tools: [Read]
/debug-distro
Trace why a CRM record was (or wasn't) routed through a distribution using the `distro-debugger` skill.
Steps
1. Read `skills/distro-debugger/SKILL.md`. 2. Check that the Chili Piper MCP is connected — call `health-ping`. If it fails, output the setup instructions from `mcp-servers/chili-piper/README.md` and stop. 3. Map the arguments to the skill inputs:
- First argument → `log_id`, `salesforce_id`, or `record_name` (detect: distribution log ID, Salesforce record ID, or a person's name). **At least one is required** — if missing, ask: *"Please provide a distribution log ID, a Salesforce record ID, or the lead/contact's name."*
- `router-id` → `router_id`. Required when a `log_id` is provided; omit to search across all routers.
- `workspace` → `workspace`. **Required when searching by `salesforce_id` or `record_name`** — if missing in that case, ask which workspace to search.
- Optional `date-range` → `date_range` (`today`, `last-7-days`, or `YYYY-MM-DD:YYYY-MM-DD`; default `last-7-days`).
4. Execute the skill's steps in order. 5. Output the log summary, the rule-by-rule stage breakdown, the plain-language diagnosis, and the specific fix. 6. Ask: *"Want me to help adjust the distribution rule, or reassign this record manually?"*
Read more
description: Debugs why a CRM record was routed (or not routed) through a Chili Piper distribution — explains each rule stage and recommends a targeted fix. argument-hint: "<log-id|salesforce-id|record-name> [router-id] [workspace] [date-range]" allowed-tools: [Read]
/debug-distro
Trace why a CRM record was (or wasn't) routed through a distribution using the `distro-debugger` skill.
Steps
1. Read `skills/distro-debugger/SKILL.md`. 2. Check that the Chili Piper MCP is connected — call `health-ping`. If it fails, output the setup instructions from `mcp-servers/chili-piper/README.md` and stop. 3. Map the arguments to the skill inputs:
- First argument → `log_id`, `salesforce_id`, or `record_name` (detect: distribution log ID, Salesforce record ID, or a person's name). **At least one is required** — if missing, ask: *"Please provide a distribution log ID, a Salesforce record ID, or the lead/contact's name."*
- `router-id` → `router_id`. Required when a `log_id` is provided; omit to search across all routers.
- `workspace` → `workspace`. **Required when searching by `salesforce_id` or `record_name`** — if missing in that case, ask which workspace to search.
- Optional `date-range` → `date_range` (`today`, `last-7-days`, or `YYYY-MM-DD:YYYY-MM-DD`; default `last-7-days`).
4. Execute the skill's steps in order. 5. Output the log summary, the rule-by-rule stage breakdown, the plain-language diagnosis, and the specific fix. 6. Ask: *"Want me to help adjust the distribution rule, or reassign this record manually?"*
Ships withchili-piper-skills
Official, first-party Skills and ChatGPT GPTs for the Chili Piper MCP server. Maintained by Chili Piper.
Get the whole plugin
Other commands on chili-piper-skills.
@chili-piperView CommandCommand
analyze-no-shows
Analyzes Chili Piper meeting no-show patterns by trigger type, routing path, rep, or workspace to surface actionable optimization opportunities.
@chili-piperView CommandCommand
audit-routing
Audit all Chili Piper concierge routers for coverage gaps, stale rules, empty distributions, and catch-all overflow.
@chili-piperView CommandCommand
build-concierge-router
Guides you through building a complete Concierge web-form router from scratch — teams, meeting types, rules, distributions, and the live router — with a…
@chili-piperView CommandCommand
check-availability
Checks why a rep or team is showing no available slots — diagnoses calendar connectivity, working hours, meeting limits, and distribution membership to find…
@chili-piperView CommandCommand
configure-concierge-ro…
Manages Concierge routers (web-form routing) — list, inspect, create, update, delete — with a dry-run plan and confirmation before any write.
@chili-piperView Command