skills.rest
Chili-Piper
Chili-PiperOFFICIAL
Explore all skills by this author →
WebsiteGitHub

meeting-inspector

Diagnose Chili Piper meeting routing and outcomes from trigger to assigned rep.

7|1|Updated May 8, 2026
Search Tags:#routing#analysis#mcp#crm#tracing#diagnose#anomaly-detection
One-click install
npx skills add https://github.com/Chili-Piper/mcp-assets --skill meeting-inspector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meeting-inspector
Source: https://github.com/Chili-Piper/mcp-assets/tree/main/skills/meeting-inspector
Command: npx skills add https://github.com/Chili-Piper/mcp-assets --skill meeting-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps diagnostic analysts understand why a Chili Piper meeting was booked, routed, and concluded, surfacing a clear next action.

Core Features & Use Cases

  • Reconstruct the full lifecycle of a meeting — from trigger and routing to rep assignment and outcome.
  • Surface anomalies and provide actionable recommendations to fix routing or CRM write-back gaps.
  • Use cases include debugging misrouted bookings, auditing CRM write-backs, and validating routing rules.

Quick Start

Provide a meeting_id or guest_email to generate a full meeting summary, routing trace, anomalies, and a recommended action.

Frequently Asked Questions about meeting-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why a Chili Piper meeting was misrouted to the wrong rep?▼

To diagnose a misrouted meeting, you trace its booking trigger, routing path, and rep assignment using a meeting_id or guest_email. This generates a routing trace and surfaces anomalies to pinpoint the root cause of the misrouted booking.

What is meeting routing analysis and how does it surface CRM write-back gaps?▼

Meeting routing analysis reconstructs the full lifecycle of a booking to audit CRM write-backs and validate routing rules. It analyzes the booking trigger and final outcome to detect anomalies, providing a structured summary of any CRM write-back gaps.

Can I audit routing rules for a specific guest_email within a certain date range?▼

Yes, you can audit routing rules by querying a specific guest_email within an optional workspace scope and date range. This validates the routing path and rep assignment to ensure the booking trigger followed the correct configuration.

What should I do when a meeting routing trace shows an anomaly in the booking outcome?▼

When a routing trace shows an anomaly, you should follow the concrete recommended next action provided in the structured output. This actionable recommendation directly addresses the detected routing or CRM write-back gap to resolve the issue.

Does meeting routing analysis work for debugging individual bookings without workspace scope?▼

Yes, meeting routing analysis works for debugging individual bookings by providing a meeting_id without requiring a workspace scope. The analysis will still return the full meeting summary, routing trace, and detected anomalies for the specific booking.

Related Skills

Explore More Data & Analytics Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
Obsidian-OwlObsidian-Owl
4

speckit-clarify

Resolve feature specification ambiguities through guided questions and recorded clarifications.

Official
Advanced
BenAIOSBenAIOS

sales-rep-analyzer

Cross-reference meeting transcripts with CRM data to generate performance reports.

Official
Advanced
FrancisVargaFrancisVarga

Anomaly Rule DSL

Define anomaly detection rules using a YAML DSL schema.

Community
Advanced