tool-discovery-skill

Detect local tools by capability and update .harness/TOOL_CONTEXT.md.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/truongnat/aix --skill tool-discovery-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-discovery-skill
Source: https://github.com/truongnat/aix/tree/main/content/skills/tool-discovery
Command: npx skills add https://github.com/truongnat/aix --skill tool-discovery-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The tool-discovery-skill addresses the issue of manual tool choice and outdated tool context, improving efficiency and reducing errors in workflows.

Core Features & Use Cases

  • Tool Discovery: Automatically detects available local tools based on capability.
  • Dynamic Routing: Routes work by capability, not by tool-name memory.
  • Contextual Updates: Updates or creates .harness/TOOL_CONTEXT.md with the latest tool information.
  • Use Case: Before verification or review, this skill ensures that the correct tools are available and configured for the task at hand.

Quick Start

Run the tool-discovery skill to update your tool context.

Frequently Asked Questions about tool-discovery-skill

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

FAQPage Schema
What is dynamic tool discovery in engineering workflows?

Dynamic tool discovery automatically detects available local tools based on their capabilities. It routes work by capability rather than tool-name memory, eliminating manual tool choice and reducing workflow errors.

How do I update my tool context before starting a code review?

To update your tool context before verification or review, run a tool discovery process that automatically updates or creates the `.harness/TOOL_CONTEXT.md` file with the latest available tool information.

How can I automate local tool selection based on capabilities?

You can automate local tool selection by running a discovery process that identifies available tools based on their capabilities. This process dynamically routes work and updates context files to reflect the latest tool configurations.

Does tool discovery require external dependencies to detect local tools?

Tool discovery operates without external dependencies to detect local tools. It autonomously identifies available tools based on their capabilities and updates your local context files accordingly.

What are the limitations of using capability routing for tool management?

Capability routing is limited to workflows requiring dynamic tool selection and local tool availability. It relies on updating context files like `.harness/TOOL_CONTEXT.md`, which may not apply to static tool environments.