repo-b-thin-waist-routing

Verifies REST routing correctness and Thin-waist endpoint policies across environments.

2|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/grtninja/skill-arbiter --skill repo-b-thin-waist-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-b-thin-waist-routing
Source: https://github.com/grtninja/skill-arbiter/tree/main/skill-candidates/repo-b-thin-waist-routing
Command: npx skills add https://github.com/grtninja/skill-arbiter --skill repo-b-thin-waist-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validate and troubleshoot thin-waist REST routing in <PRIVATE_REPO_B>. Use when changing /v1 models/chat/vision routes, async job queue endpoints, connector routing policy, or bind/exposure behavior.

Core Features & Use Cases

  • Verifies routing correctness for thin-waist endpoints across local, staging, and production environments.
  • Checks that routing decisions remain centralized in the ModelRouter and validates OpenAI-compatible façade routes.
  • Provides a checklist-based quick verification to reproduce and diagnose routing issues.

Quick Start

Run a quick verification by issuing sample curl calls to the thin-waist endpoints to confirm routing integrity.

Frequently Asked Questions about repo-b-thin-waist-routing

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

FAQPage Schema
How do I verify thin-waist REST routing correctness for /v1 models and chat endpoints?

Verify thin-waist REST routing by running sample curl calls against /v1 models, chat, and vision endpoints to confirm routing integrity and validate OpenAI-compatible façade routes across local, staging, and integration environments.

What is a thin-waist routing policy and when do I need to validate it?

A thin-waist routing policy centralizes routing decisions in the ModelRouter to enforce deterministic checks for loopback binds and LAN guard defaults. Validate it when changing connector routing policy, async job queue endpoints, or bind/exposure behavior.

How do I diagnose REST routing issues in staging and integration environments?

Diagnose REST routing issues using a checklist-based quick verification that reproduces problems by issuing sample curl calls to thin-waist endpoints, checking queue state and exposure across local, staging, and integration environments.

Does the ModelRouter validate OpenAI-compatible façade routes and async job queue endpoints?

Yes, the ModelRouter validates OpenAI-compatible façade routes and checks routing correctness for async /api/jobs endpoints, including queue state and exposure checks across local, staging, and integration environments.

What are the limitations when validating loopback binds and LAN guard defaults?

Validation is limited to deterministic checks for loopback binds and LAN guard defaults within thin-waist endpoints in repo B shims, and does not cover non-REST protocols or routing logic outside the centralized ModelRouter.