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
/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 confirmation checkpoint before anything is created.
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
/build-concierge-router
Context preview
What this command does when you run it.
Guides you through building a complete Concierge web-form router from scratch — teams, meeting types, rules, distributions, and the live router — with a confirmation checkpoint before anything is created.
Command definition
build-concierge-router.mddescription: Guides you through building a complete Concierge web-form router from scratch — teams, meeting types, rules, distributions, and the live router — with a confirmation checkpoint before anything is created.
argument-hint: "[workspace] [requirements] [--build]"
allowed-tools: [Read]
/build-concierge-router
Build a new Concierge router end to end using the `concierge-router-builder` skill.
> ⚠️ This skill **writes to Chili Piper** and publishes a **live** router. It creates many > objects (teams, meeting types, rules, distributions) and is **not transactional** — a > mid-build failure leaves earlier objects behind. It always runs the interview and presents > a full plan first; nothing is created until you confirm. Data fields and web-form mapping > are **UI-only prerequisites** the API cannot do.
Steps
1. Read `skills/concierge-router-builder/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 → `workspace` (optional; asked if missing).
- Remaining text → `requirements` (optional free-text to pre-fill the interview).
- `--build` → `dry_run: false`. **Without `--build`, always run with `dry_run: true`.**
4. Execute the phases in order — Phase 0 prerequisites, Phase 1 interview, Phase 2 confirmation checkpoint (STOP for confirmation), Phase 3 build, Phase 4 verify & hand off. 5. Output the build plan (dry run) or the built objects + booking slug + go-live checklist (after `--build`). 6. Tip: to *edit* an existing router use `/configure-concierge-router`; to *diagnose* one use `/debug-concierge` or `/audit-routing`.
Read more
description: Guides you through building a complete Concierge web-form router from scratch — teams, meeting types, rules, distributions, and the live router — with a confirmation checkpoint before anything is created. argument-hint: "[workspace] [requirements] [--build]" allowed-tools: [Read]
/build-concierge-router
Build a new Concierge router end to end using the `concierge-router-builder` skill.
> ⚠️ This skill **writes to Chili Piper** and publishes a **live** router. It creates many > objects (teams, meeting types, rules, distributions) and is **not transactional** — a > mid-build failure leaves earlier objects behind. It always runs the interview and presents > a full plan first; nothing is created until you confirm. Data fields and web-form mapping > are **UI-only prerequisites** the API cannot do.
Steps
1. Read `skills/concierge-router-builder/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 → `workspace` (optional; asked if missing).
- Remaining text → `requirements` (optional free-text to pre-fill the interview).
- `--build` → `dry_run: false`. **Without `--build`, always run with `dry_run: true`.**
4. Execute the phases in order — Phase 0 prerequisites, Phase 1 interview, Phase 2 confirmation checkpoint (STOP for confirmation), Phase 3 build, Phase 4 verify & hand off. 5. Output the build plan (dry run) or the built objects + booking slug + go-live checklist (after `--build`). 6. Tip: to *edit* an existing router use `/configure-concierge-router`; to *diagnose* one use `/debug-concierge` or `/audit-routing`.
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
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 CommandCommand
configure-distro-route…
Manages Distro (lead-routing) routers — list, inspect, create, update, activate/deactivate, delete — with a dry-run plan and confirmation before any write.
@chili-piperView Command