routing-tables

Name: routing-tables
Availability: InStock
Author: grimblaz

Centralize routing data from JSON configs for deterministic agent dispatch.

3|Updated Dec 7, 2025

Search Tags:#routing #reference #dispatch #assets #deterministic #prompts

Ready to run

npx skills add https://github.com/Grimblaz/agent-orchestra --skill routing-tables

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: routing-tables
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/routing-tables
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill routing-tables

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Centralizes canonical routing data to avoid duplicating prompt prose and to ensure consistent routing decisions across agents.

Core Features & Use Cases

Centralizes routing tables from assets/routing-config.json and gate criteria from assets/gate-criteria.json for deterministic lookups.
Supports routing for specialist_dispatch, review_mode_routing, and surface_identification to guide agent behavior without embedding runtime state.
Provides a stable reference for updating routing metadata and for deterministic prompts in downstream tooling.

Quick Start

Load the latest canonical routing data from assets/routing-config.json and assets/gate-criteria.json to drive deterministic prompts and routing decisions.

Frequently Asked Questions about routing-tables

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

FAQPage Schema

What is deterministic agent dispatch and when do I need centralized routing data?▼

Deterministic agent dispatch uses centralized routing tables to guide consistent dispatch decisions without embedding runtime state. You need it when multiple agents require a single canonical reference for routing mappings and gate evaluation criteria.

How do I centralize routing configuration for specialist dispatch and review mode routing?▼

Centralize routing configuration by loading canonical data from routing-config.json and gate-criteria.json assets. These files provide deterministic lookup tables for specialist_dispatch, review_mode_routing, and surface_identification to guide agent behavior.

Can I use JSON assets to drive deterministic prompts for downstream agent tooling?▼

Yes, JSON assets expose canonical routing data that serves as a stable reference for deterministic prompts in downstream tooling. Loading routing-config.json and gate-criteria.json provides the mappings needed to drive prompt generation and routing decisions.

What's the best way to avoid duplicating prompt prose for agent routing decisions?▼

The best way to avoid duplicating prompt prose is centralizing canonical routing data in dedicated JSON assets. This ensures consistent routing decisions across agents by providing a single source of truth for dispatch and gate evaluation mappings.

Does centralized routing data support surface identification for agent behavior?▼

Yes, centralized routing data supports surface_identification alongside specialist_dispatch and review_mode_routing. The routing tables provide the deterministic mappings needed to identify surfaces and guide agent behavior without relying on embedded runtime state.

What are the limitations of using static JSON routing tables for agent dispatch?▼

Static JSON routing tables provide deterministic lookups but do not embed runtime state, meaning agents must reference the canonical assets externally. Routing decisions are constrained to the mappings defined in routing-config.json and gate-criteria.json.