skill-management

Token usage during tool routing and execution is reduced by isolating tool definitions in a dedicated subagent context. This approach offloads tool execution overhead from the main agent, minimizing overall token consumption while maintaining scalable orchestration.

Semantic categorization for tool routing groups tools into domains like Browser, GitHub, GraphQL, and Docs. This classification enables fast, deterministic tool discovery using a cached index, ensuring safe and precise tool selection across different task types.

Deterministic tool discovery requires configuring a tool cache at the .opencode/skill-tools.json file path. This cached index allows the routing system to quickly map parameters and select appropriate tools without scanning definitions repeatedly.

Yes, browser, GitHub, and GraphQL tools can be routed through a single subagent context. The system applies category-aware routing with strict parameter mapping to ensure deterministic, safe tool selection across these diverse domains.

Strict parameter mapping is required during tool execution to ensure deterministic and safe tool selection. It prevents ambiguous or incorrect parameter passing when routing complex tasks through the subagent context to the target tools.

The limitation of using a cached index for tool routing is that it requires the .opencode/skill-tools.json cache to be actively maintained. If the cache becomes outdated, tool discovery and category-aware routing may fail to recognize newly added or modified tool definitions.