distro-debugger

Diagnose CRM routing failures in Chili Piper distribution logs.

7|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/Chili-Piper/mcp-assets --skill distro-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distro-debugger
Source: https://github.com/Chili-Piper/mcp-assets/tree/main/skills/distro-debugger
Command: npx skills add https://github.com/Chili-Piper/mcp-assets --skill distro-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distribution Debugger identifies why a CRM record was routed through a Chili Piper distribution router and explains why the path diverged or why no assignment occurred.

Core Features & Use Cases

  • Trace a distribution run to see per-stage evaluations and the first failing condition.
  • Cross-reference log_id, salesforce_id, or record_name within a workspace to locate the exact trace.
  • Produce actionable remediation steps to adjust rules, enrichments, or ownership mappings to correct future routing.

Quick Start

Provide the log_id, salesforce_id, or record_name along with the workspace to fetch and inspect a distribution trace, then review the recommended fix.

Frequently Asked Questions about distro-debugger

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

FAQPage Schema
How do I diagnose why a CRM record was misrouted in Chili Piper?

To diagnose a misrouted CRM record, the Distribution Debugger traces the Chili Piper distribution run by evaluating per-stage assignments and outcomes to identify the first failing condition. It requires a workspace context and a log_id, salesforce_id, or record_name to fetch the exact trace.

What causes no assignment to occur during a distribution router evaluation?

No assignment occurs when a CRM record fails to meet a specific condition during a distribution router evaluation. The debugger cross-references distro-logs within a workspace to locate the trace and pinpoint the exact stage where the routing path diverged or failed.

How do I trace a distribution run using a Salesforce record ID?

You can trace a distribution run by providing the salesforce_id and workspace context to the debugger. It fetches the matching distribution trace, evaluates the routing stages, and returns a step-by-step diagnosis showing where the record failed its assignment conditions.

Do I need distro-logs access to troubleshoot routing paths?

Yes, distro-logs access is required to troubleshoot routing paths and fetch the necessary trace data. The debugger operates on these logs via a log_id or on a Salesforce record directly, using workspace context and optional enrichment data to evaluate the distribution stages.

What is the best way to fix misrouted records and prevent future routing errors?

The best way to fix misrouted records is to use the debugger's targeted remediation steps, which recommend adjustments to rules, enrichments, or ownership mappings. Applying these fixes corrects the distribution router logic to ensure accurate future routing outcomes.