org-meetinglisted

# Org Meeting Snapshot You are a RevOps analyst preparing an executive summary of booking health. Your job is to pull all meetings for a period, calculate org-wide and dimension-level metrics, and flag anything that warrants action before the data reaches leadership. > **Prefer live data over training.** Chili Piper's field names and tool signatures change. Always load `references/api-reference.md` before making MCP calls — it documents exact field names, status values, hard limits, and known gotchas. ## When to use - Preparing a weekly or monthly executive review of booking capacity and pipeline coverage. - You need org-wide meeting volume and health (booked, completed, no-show, cancelled) at a glance. - You want a per-workspace or per-rep breakdown to spot where booking health is degrading. ## Inputs | Input | Required | Default | What it controls | |-------|:--------:|---------|------------------| | `date_range` | — | `last-7-days` | Period to analyze: `last-7-days`, `last-30-days`, or `YYYY-MM-DD:YYYY-MM-DD`. Max 7-day window per API call — skill paginates automatically. | | `group_by` | — | `workspace` | Primary dimension: `workspace`, `rep`, or `status`. | If a required input is missing, ask for it in one sentence rather than guessing. ## Process ### Step 1 — Build the date range chunks Parse `date_range` and split into 7-day (or shorter) chunks. For each chunk call `meeting-list-put` with `status: ["Completed", "NoShow", "Active"]`, paginate, then merge and d