routing-debug

Diagnose routing decisions by exposing keyword matches, confidence scores, and competing agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jrc1883/popkit-claude --skill routing-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routing-debug
Source: https://github.com/jrc1883/popkit-claude/tree/main/skills/pop-routing-debug
Command: npx skills add https://github.com/jrc1883/popkit-claude --skill routing-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugs and analyzes agent routing decisions, showing keyword matches and competing agents.

Core Features & Use Cases

  • Explain routing: reveals why a particular agent was chosen.
  • Trace path: follows the decision tree to diagnose routing issues.
  • Compare options: shows competing agents and scores.

Quick Start

/routing-debug "fix the authentication bug" to see routing decisions.

Frequently Asked Questions about routing-debug

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

FAQPage Schema
Why did the router select a particular agent for my prompt?

Routing-debug diagnoses agent selection by exposing keyword matches, confidence scores, and competing agents. It reveals which prompt terms triggered the routing decision and shows alternative agents that were considered.

How do I trace why an unexpected agent was chosen?

Use routing-debug to follow the decision tree and see which keywords matched, their confidence scores, and why one agent ranked higher than others. This reveals the reasoning behind routing paths that seem incorrect.

Can I see competing agents and their scores when debugging routing?

Yes. Routing-debug displays all competing agents alongside their confidence scores, letting you compare why the selected agent won and understand trade-offs between routing options.

What information does routing analysis provide for auditing?

Routing-debug outputs keyword matches, confidence scores, and competing agents with full routing traces. This supports auditing by documenting which signals influenced each routing decision.

How do I start debugging a routing decision?

Run routing-debug with the prompt you want to analyze—for example, `/routing-debug "fix the authentication bug"` to see routing decisions, keyword matches, and competing agents for that input.