ariadne-core

Skill routing works by dispatching user requests to designated sub-skills based on intent. It preserves user intent through well-defined routing rules, directing general questions, document actions, and explicit skill invocations to the appropriate implementations.

To route document actions like ingest and extract, the system dispatches these requests to the ariadne-document-intelligence skill. This ensures document-specific operations are handled by the appropriate sub-skill implementation.

Orchestrating multiple skills requires a central entry point that routes requests to designated sub-skills. This approach dispatches calls to specific implementations while preserving user intent throughout the workflow.

Yes, you can use this routing plugin for general onboarding questions. It directs general queries such as "what is ariadne" to the ariadne-core-walkthrough skill to provide the appropriate informational responses.

You should invoke a dedicated skill router when handling explicit skill requests like "run the install skill." The router dispatches these calls to the ariadne-core-router implementation rather than answering from the entry point file.

A workflow needs a skill dispatch entry point to prevent logic fragmentation. It routes user requests across general questions, document actions, and explicit invocations, preserving user intent through well-defined routing rules.