jido-skill-router

Route tasks across Jido skills using an anchor-based routing workflow.

48|21|Updated Jan 25, 2025
One-click install
npx skills add https://github.com/agentjido/jido_run --skill jido-skill-router-agentjido
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jido-skill-router
Source: https://github.com/agentjido/jido_run/tree/main/priv/skills/arrowcircle-jido-skills/skills/jido-skill-router
Command: npx skills add https://github.com/agentjido/jido_run --skill jido-skill-router-agentjido

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Routing decisions among Jido package skills can be ambiguous, leading to misrouted work and fragmented workflows. This skill provides a centralized routing framework to identify the anchor skill and coordinate subsequent handoffs to adjacent skills.

Core Features & Use Cases

  • Anchor-based routing: determines the primary package skill for a task and isolates it to prevent cross-skill bleed.
  • Explicit handoffs: prescribes a minimal, ordered handoff sequence (anchor -> adjacent) to maintain clear task provenance.
  • Reference-driven routing map: leverages the skill-manifest in references to resolve relationships and recommended skill paths.

Quick Start

Route a cross-skill task by identifying the anchor skill and adding one adjacent skill when boundaries cross.

Frequently Asked Questions about jido-skill-router

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

FAQPage Schema
How do I route tasks across multiple skills to prevent workflow fragmentation?

Route tasks across multiple skills by identifying an anchor skill to handle the primary workload, then adding adjacent skills only when task boundaries cross. This explicit handoff sequence prevents fragmented workflows and misrouted operations.

What is anchor-based skill orchestration and when do I need it?

Anchor-based skill orchestration is a routing method that isolates a primary skill to process a task, preventing cross-skill bleed. You need it for multi-skill scenarios where unmanaged handoffs would cause ambiguous task execution.

How do I manage multi-skill handoffs without losing task provenance?

Manage multi-skill handoffs by applying a minimal, ordered sequence from the anchor skill to adjacent skills. This routing workflow keeps handoffs explicit and maintains clear task provenance throughout the orchestration.

Can I resolve skill routing paths using a manifest reference?

Yes, routing paths are resolved using a skill-manifest reference map. This machine-readable inventory defines skill relationships and provides structured prompts to ensure correct routing decisions across the workflow.

What is the best way to coordinate cross-skill boundaries during task execution?

The best way to coordinate cross-skill boundaries is to load an anchor skill first, then add one adjacent skill only when the boundary is crossed. This centralized routing framework ensures clear and minimal handoffs.