jido-skill-router

To route tasks across Jido skills, identify the anchor capability and load only the relevant package skill. The router uses references/skill-manifest.yaml to provide deterministic handoffs and minimize cross-skill calls.

Anchor-based routing in skill orchestration identifies the primary capability required for a task and loads only that specific skill. Adjacent skills are loaded only when a task crosses their boundaries.

Minimize cross-skill calls by applying boundary-aware handoffs that sequence only the necessary package skills. The router consults skill-manifest.yaml to avoid loading the full ecosystem for a single handoff.

Yes, you can use a machine-readable skill manifest to govern task hand-offs. The router consults references/skill-manifest.yaml for skill inventory and routing rules to determine the correct handoff order.

No, the Jido skill router does not require loading the full ecosystem. It selects the anchor skill and loads adjacent skills only when boundaries are crossed, optimizing both latency and accuracy.

The best way to sequence model selection and action execution is using the router to order jido-action, jido, and jido-signal. This provides a concise handoff order without full ecosystem loading.