Agent skill

tool-search

Semantic tool search with embeddings for scalable tool discovery. Enables on-demand tool loading to reduce context usage by 90%+ for large tool libraries.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill tool-search-oimiragieo-agent-studio-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Version: 1.0
Path: skills/agent/tool-search-oimiragieo-agent-studio-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

**References (archive):** [SCAFFOLD_SKILLS_ARCHIVE_MAP.md](../../docs/SCAFFOLD_SKILLS_ARCHIVE_MAP.md) — embedding/semantic tool discovery from everything-claude-code backend-patterns, tdd-workflow. # Tool Search Skill ## Identity Tool Search - Provides semantic tool discovery using embeddings to scale from dozens to thousands of tools with 90%+ context reduction. ## Capabilities - **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 ## The Problem Traditional tool loading: - All tools loaded upfront - 58 tools = ~55K tokens - Context fills quickly - Hard to scale beyond ~100 tools ## The Solution Tool Search with Embeddings: - Only Tool Search Tool loaded initially (~500 tokens) - Tools discovered on-demand via semantic search - 3-5 relevant tools loaded per search (~3K tokens) - Total: ~8.7K tokens vs. ~77K traditional (85% reduction) ## How It Works 1. **Initial State**: Only Tool Search Tool + critical tools loaded 2. **Tool Discovery**: Agent searches for tools based on t

What's inside
Steps it walks through
  1. Identity
  2. Capabilities
  3. The Problem
  4. The Solution
  5. How It Works
  6. Configuration
  7. MCP Configuration (.claude/.mcp.json)
  8. Always Load Critical Tools
  9. Usage Patterns
  10. When to Use Tool Search
  11. Tool Discovery
  12. Best Practices
  13. 1. Clear Tool Names and Descriptions
  14. 2. System Prompt Guidance
Ships with 1 file
  • metadata.json
Commands it runs
Search for git-related tools
node .claude/tools/tool_search.mjs --query "git"
Search for database tools
node .claude/tools/tool_search.mjs --query "database" --limit 3
Search for testing tools
node .claude/tools/tool_search.mjs --query "testing"
More from claude-skill-registry
All skills →
About this skill
What does the tool-search skill do?

Semantic tool search with embeddings for scalable tool discovery. Enables on-demand tool loading to reduce context usage by 90%+ for large tool libraries.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill tool-search-oimiragieo-agent-studio-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going