routing-explainer

Explain routing decisions for user requests with structured decision overviews.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill routing-explainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routing-explainer
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.codex/skills/routing-explainer
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill routing-explainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The routing explainer clarifies and documents routing choices to users, increasing transparency and trust in automated workflows.

Core Features & Use Cases

  • Explain pre-request routing decisions when a user requests --explain-routing or mentions routing issues.
  • Provide a structured decision outline including quick checks, skill-match signals, and agent collaboration cues.
  • Useful for auditing and optimizing routing policies in multi-skill workflows.

Quick Start

Explain routing decision for the current user request.

Frequently Asked Questions about routing-explainer

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

FAQPage Schema
How do I explain routing decisions for user requests in a multi-skill workflow?

Routing decisions for user requests are explained by outputting a structured overview of quick checks, skill-match signals, and agent collaboration cues. This clarifies routing choices to increase transparency and trust in automated workflows.

What is a structured routing decision overview used for during workflow debugging?

A structured routing decision overview is used for auditing and optimizing routing policies in multi-skill workflows. It provides transparency by documenting trigger conditions, frontmatter constraints, and routing rules applied to user requests during debugging.

Can I audit routing logic using only trigger conditions and frontmatter constraints?

Yes, you can audit routing logic using trigger conditions and frontmatter constraints. The routing explainer requires access to these specific routing rules to generate a structured decision outline and successfully audit the workflow's routing behavior.

What's the best way to debug multi-skill workflow routing issues?

The best way to debug multi-skill workflow routing issues is to request a routing explanation. This generates a structured decision outline including quick checks and skill-match signals, applying directly during audits of routing logic and debugging sessions.

When should I request a routing explanation for agents?

You should request a routing explanation for agents when you mention routing issues or need to audit routing policies. It applies during audits of routing logic and debugging of multi-skill workflows to output a clear decision overview.