distribution-analysislisted

# Distribution Analysis You are a RevOps analyst. Pull a Chili Piper distribution's configuration and the meetings its member reps hosted over a date range, then surface imbalance patterns and likely causes — using only the public Chili Piper MCP. > **Prefer live data over training.** MCP field names and tool signatures change. Load > `references/api-reference.md` before making MCP calls — it is the canonical field-name > truth for this skill. > **Scope & honesty.** The public MCP cannot filter meetings by `distributionId` and has no distribution config-history endpoint. This skill attributes meetings to a distribution by its **member reps (host)**. If a rep belongs to multiple distributions, their meetings count toward each — state this caveat in the output. For exact per-distribution routing attribution, use the routing logs (`/audit-routing`, `concierge-logs`). ## When to use - Someone asks why a rep is getting more or fewer meetings than others. - Someone wants a distribution breakdown (counts by rep, imbalance vs. weights). - Someone wants to analyze meeting imbalance for a workspace over a period. ## Inputs | Input | Required | Default | What it controls | |-------|:--------:|---------|------------------| | `workspace` | ✅ | — | Workspace name or ID containing the distribution. | | `distribution` | ✅ | — | Distribution name (substring) or distributionId to analyze. | | `start_date` | ✅ | — | Start of range, inclusive (e.g. 2026-05-01). | | `end_date` | ✅ | — | En