bedrud-dispatch

Route tasks to leaf skills by task type with fallback routing.

6|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/themadorg/bedrud --skill bedrud-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bedrud-dispatch
Source: https://github.com/themadorg/bedrud/tree/main/.agents/skills/bedrud-dispatch
Command: npx skills add https://github.com/themadorg/bedrud --skill bedrud-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routing tasks to the correct leaf skill based on task type to reduce manual guessing and speed up task dispatch.

Core Features & Use Cases

  • Automatic leaf-skill resolution: map a given task type to the appropriate bedrud-<leaf> skill using task keywords.
  • Fallback routing: if a task is unclear, route to bedrud-http + bedrud-data for safe handling.
  • Cross-domain support: usable across backend, frontend, and API contexts to maintain a consistent dispatch strategy.

Quick Start

Provide a task type such as 'auth' or 'http' and Bedrud will route to the corresponding leaf skill.

Frequently Asked Questions about bedrud-dispatch

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

FAQPage Schema
How do I automatically route tasks to the correct sub-skill based on task type?

Task routing inspects task keywords and maps them to the appropriate bedrud leaf skill, such as bedrud-auth or bedrud-http. This reduces manual guessing and speeds up dispatch across backend, frontend, and API contexts.

What happens when task routing encounters an unclear or ambiguous task type?

When task routing encounters an unclear task type, it applies a safe fallback to bedrud-http and bedrud-data. This ensures unclear tasks are still handled safely without failing the dispatch process.

How do I dispatch an auth task to its corresponding leaf skill?

To dispatch an auth task, provide the task type 'auth' to the routing mechanism. The dispatcher inspects the keyword and automatically loads the bedrud-auth leaf skill to handle the operation.

Can I use task routing across backend, frontend, and API development contexts?

Yes, task routing supports cross-domain usage across backend, frontend, and API contexts. It maintains a consistent dispatch strategy to load the correct sub-skill regardless of the development domain.

What is the best way to dispatch HTTP requests to a specific handler skill?

The best way to dispatch HTTP requests is to provide the 'http' task type to the routing mechanism. It maps the keyword and automatically loads the bedrud-http leaf skill for handling.

Why does task routing fail to load the expected leaf skill for my task?

Task routing fails to load the expected leaf skill when the task type is unclear or lacks matching keywords. In these cases, it applies a safe fallback to bedrud-http and bedrud-data instead.