tool-search

Match task context to relevant tools using embeddings and load them on demand.

36|6|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/oimiragieo/LLM-RULES --skill tool-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-search
Source: https://github.com/oimiragieo/LLM-RULES/tree/main/.claude/skills/tool-search
Command: npx skills add https://github.com/oimiragieo/LLM-RULES --skill tool-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finding the right tools in large tool libraries is hard and context-heavy. This Skill enables semantic discovery and on-demand loading to dramatically reduce context usage.

Core Features & Use Cases

  • Semantic Tool Search: Find relevant tools based on task context
  • Embedding-Based Matching: Use embeddings for accurate tool discovery
  • On-Demand Loading: Load tools only when needed
  • Context Efficiency: 90%+ reduction in tool definition tokens

Quick Start

Search for a GitHub PR creation tool by task: 'github pull request creation'

Frequently Asked Questions about tool-search

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

FAQPage Schema
How does semantic tool search reduce context usage in large tool libraries?

Semantic tool search uses embeddings to match task context against tool definitions, loading only 3-5 relevant tools on-demand instead of all tools upfront. This achieves 90%+ reduction in tool definition tokens while maintaining access to full tool libraries with 10+ tools.

Can I use embedding-based tool discovery with GitHub, Jira, and Slack integrations?

Yes. The Skill applies semantic matching to tool libraries encompassing GitHub interactions, Jira tickets, and Slack integrations, identifying and loading relevant tools for each task without pre-loading entire integration suites.

How do I search for tools by task context instead of tool names?

Describe your task naturally—for example, 'github pull request creation'—and the embedding-based matching identifies semantically relevant tools from your library, then loads their full definitions on-demand for execution.

What happens if a tool isn't found during on-demand loading?

The Skill includes graceful error handling to manage cases where matched tools fail to load, while keeping core tools always loaded for reliability so task execution doesn't break on edge cases.

What scale of tool libraries does this approach work best for?

Tool search is optimized for libraries with 10+ tools. At this scale, embedding-based matching and on-demand loading deliver the most significant context savings compared to loading all tool definitions upfront.