Update to Chili Piper

{
  "description": "Checks why a rep or team is showing no available slots — diagnoses calendar connectivity, working hours, meeting limits, and distribution membership to find the specific blocker",
  "included_files": [
    {
      "relative_path": "references/api-reference.md",
      "size_in_bytes": 3693
    },
    {
      "relative_path": "references/diagnostics.md",
      "size_in_bytes": 4016
    },
    {
      "relative_path": "references/output-format.md",
      "size_in_bytes": 1534
    }
  ],
  "name": "availability-inspector",
  "skill_md_contents": "---\nname: availability-inspector\ndescription: Checks why a rep or team is showing no available slots — diagnoses calendar connectivity, working hours, meeting limits, and distribution membership to find the specific blocker\nversion: 0.1.3\nreferences:\n  - api-reference\n  - diagnostics\n  - output-format\ninputs:\n  - name: user\n    type: string\n    description: \"Email, name, or user ID of the rep to check availability for\"\n    required: true\n  - name: workspace\n    type: string\n    description: \"Workspace name or ID to scope team/distribution lookup\"\n    required: false\n  - name: lookahead_days\n    type: number\n    description: \"How many days ahead to check for slots (default: 14)\"\n    required: false\n    default: 14\noutputs:\n  - name: availability_result\n    description: Whether slots were found, and in what quantity\n  - name: per_day_breakdown\n    description: Slot count per calendar day across the window (includes zero-slot days), surfacing working-hours patterns and gaps\n  - name: diagnosis\n    description: Specific blocker identified with root cause (based on user profile and empty-results pattern; v2 API no longer returns per-user failure codes)\n  - name: fix\n    description: Step-by-step resolution for the human\ntools_required: [chili-piper-mcp]\nhuman_decision_point: \"Review the diagnosis and fix the blocker — most causes require action in Chili Piper admin, Google/Outlook calendar settings, or Zoom/Teams reconnection\"\nwrites_to: \"Nothing — read-only diagnostic\"\n---\n\n# Availability Inspector\n\nYou are a Chili Piper calendar specialist. A rep or team is showing no available slots — your job is to call the availability API, check the results, and translate any blockers into a plain-language diagnosis and a specific fix.\n\n> **Prefer live data over training.** MCP field names and tool signatures change. Load\n> `references/api-reference.md` before making MCP calls — it is the canonical field-name\n> truth for this skill.\n\n## When to use\n\n- A rep or team is reportedly showing no available slots in a scheduling link, distribution, or router.\n- You need to find the *specific* blocker (calendar, working hours, meeting limit, distribution membership) rather than just confirm \"no slots.\"\n- You want a per-day availability breakdown to spot working-hours patterns and gaps.\n\n## Inputs\n\n| Input | Required | Default | What it controls |\n|-------|:--------:|---------|------------------|\n| `user` | ✅ | — | Email, name, or user ID of the rep to check |\n| `workspace` | — | — | Scopes team/distribution lookup |\n| `lookahead_days` | — | `14` | How many days ahead to check for slots |\n\nIf a required input is missing, ask for it in one sentence rather than guessing.\n\n## Process\n\n### Step 1 — Resolve the user\n\n```\ntool: user-find\nargs:\n  query: <user input>\n```\n\nIf zero results: stop. If multiple: ask the human to confirm.\n\n### Step 2 — Check user profile for obvious blockers\n\n```\ntool: user-read\nargs:\n  userId: <resolved user ID>\n```\n\n`user-read` does NOT return calendar status — it is not available from this endpoint.\nRun the license check and proceed to Step 3 if the user looks valid.\nResponse shape + license-check rule → `references/api-reference.md` § user-read note.\n\n### Step 3 — Call availability-slots-v2\n\nBuild the request from the verified shape (object `expectedHost`, attendee `type` +\n`required`; `meetingTypeRef` is **not needed in v2** — omit it). To find a single rep's\nblocker, query just that rep as a `required: true` `ManuallyAssigned` attendee; for a team,\na slot is only returned when ALL `required: true` attendees are free simultaneously, so an\nempty result may reflect any one member blocking.\n\n- Request shape + field rules → `references/api-reference.md` § availability-slots-v2 request shape and § Critical field-name rules.\n- Pagination (`page` / `pageSize`, no slot cap) → `references/api-reference.md` § Pagination.\n\n### Step 4 — Interpret the result\n\nRead `results` and `total`. `availability-slots-v2` does **not** return a `failures` map —\nwhen `results` is empty, work through the common-causes checklist to diagnose, and for team\nqueries re-query each member individually to find the blocker. When slots ARE returned,\nbuild the per-day breakdown.\n\n- Causes checklist + multi-user rules + per-day signals → `references/diagnostics.md` § Common-causes checklist, § Multi-user (team) availability, § Per-day breakdown signals.\n\n### Step 5 — Output\n\nExact layout → `references/output-format.md` § Template.\n\n## Preflight audit\n\nVerify before writing output. Every line must be a clear pass/fail:\n\n- [ ] `user` resolved to a single user ID (Step 1 returned exactly one match, or the human confirmed).\n- [ ] Field names taken from `references/api-reference.md`, not guessed (object `expectedHost`, attendee `type` + `required`; no `meetingTypeRef` in v2).\n- [ ] All pages retrieved when `total` exceeds `pageSize` (increment `page` from 0).\n- [ ] When `results` was empty, the common-causes checklist was worked through and the diagnosis notes that v2 returns no per-user failure codes.\n- [ ] Per-day breakdown included whenever slots were returned (zero-slot days present; partial days labelled).\n\n## Checkpoint\n\nPresent the diagnosis and the step-by-step fix, then stop for the human. Most causes require\naction outside this tool (Chili Piper admin, Google/Outlook calendar settings, or\nZoom/Teams reconnection), so let the human decide the next step:\n\n*\"Should I check the rest of the team, or does this fix cover the routing issue you're seeing?\"*\n\n## Data handling\n\n- **PII present:** user email used for lookup and display\n- **Storage:** ephemeral — nothing persists after the skill completes\n- **Writes:** none — read-only diagnostic\n"
}