klh-dispatch

Detects task type and routes work to the appropriate klh-* skill.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/klh/skills --skill klh-dispatch-klh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: klh-dispatch
Source: https://github.com/klh/skills/tree/main/.well-known/agent-skills/klh-dispatch
Command: npx skills add https://github.com/klh/skills --skill klh-dispatch-klh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task could match multiple skills, choosing the right one manually is error-prone and slow. This Skill acts as a single entry-point orchestrator that detects the user's intent and dispatches to the correct klh-* skill, so the user never has to memorize the routing table. ## Core Features & Use Cases - Intent-Based Routing: Maps user requests (find bugs, debug, simplify code, write tests, validate schemas, and more) to the matching klh-* skill via a routing table. - Multi-Skill Loop: For complex tasks, it plans a skill chain, confirms it with the user, executes each skill in order, and verifies output after each phase. - Safety Guardrails: Enforces hard caps (max 5 loops, 50 tool calls), never auto-commits or pushes, and escalates to the user after repeated failures. - Use Case: A user says "klh this: my API endpoint returns wrong data and I need tests." The dispatcher chains klh-systematic-debugging for root cause analysis, then klh-testing-patterns for regression tests, verifying each step. ## Quick Start Say "dispatch this task" or "klh this" followed by your task, and the orchestrator will pick and run the right skill for you.

Frequently Asked Questions about klh-dispatch

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

FAQPage Schema
How do I automatically pick the right skill for a task?

Invoke the dispatcher by saying "dispatch", "klh this", or describing a task that could match multiple skills. It detects the intent, consults its routing table, and invokes the matching klh-* skill without you naming it.

How does the dispatcher handle tasks needing multiple skills?

It runs a four-phase loop: scope the task, plan a skill chain and confirm it with you, execute each skill in order with output verification, then run a final bug check. It reports results and stops without committing anything.

When should I not use the dispatch orchestrator?

Skip it when you already know which klh-* skill you want, when the task is a one-line fix, or when you are asking a factual question. Direct skill invocation avoids the orchestration overhead.

What safety limits does the dispatcher enforce?

It caps execution at 5 iteration loops and 50 tool calls, stops and escalates if a skill fails twice, and never auto-commits, pushes, merges, or opens pull requests without explicit user direction.

Can the dispatcher run skills in parallel?

Yes, for plans with 3 or more independent tasks it spawns up to 5 parallel agents, each scoped with a cohesion contract covering shared types and naming. It allows at most 3 reconciliation rounds to resolve integration issues.