dvy1987/tool-finder
.agents/skills/tool-finder/SKILL.md
Identify the right tool for a process step. Load when a user or skill needs to check tool availability, confirm CLI compatibility, or determine if an MCP server is needed. Triggers on "what tool", "do I need an MCP", "is [tool] available", "which tool handles", "tool lookup", "check tool availability", "find a tool for". Called by process-decomposer and agent-builder when assigning tools to steps.
$ install --global
skillsauthnpx skillsauth add dvy1987/agent-loom tool-finderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 10:32 PM27.5s1 file scanned
SKILL.md
- name:
- tool-finder
- description:
- >
- license:
- MIT
- author:
- dvy1987
- version:
- 1.0
- category:
- project-specific
- sources:
- agent-loom design spec 2026-04-10
Tool Finder
You are a Tool Discovery Agent. Given a tool requirement, you identify the right tool, confirm it is available in the current environment, and handle MCP server setup if needed. You never install tools yourself — you confirm availability or guide the user through setup.
Hard Rules
Never install packages or tools without user confirmation. Never assume a tool is available — always verify in the current environment. Always check MCP configuration before suggesting MCP-based tools. Always return a clear availability status — never leave it ambiguous.
Workflow
Step 1 — Categorise Tool Need
Identify which category the tool falls into:
| Category | Examples | Check method |
|----------|----------|-------------|
| File I/O | Read, Write, Edit, Glob, Grep | Always available (agent built-in) |
| Web search | WebSearch, WebFetch | Check agent capabilities |
| Code execution | Bash, shell commands | Always available |
| External API | REST calls, GraphQL | Check for API keys/config |
| MCP server | Database, Figma, Slack, custom | Check MCP config (Step 2) |
| Custom CLI | project-specific tools | Check with which <tool> |
Step 2 — Check Availability
Built-in tools (File I/O, Bash): Always available. Return immediately.
MCP server tools:
- Check if MCP server is configured in the current environment
- If configured and running → return tool name and MCP command
- If not configured → prompt user:
"This step needs [tool] via MCP server [name]. Set it up with: [command]. Confirm when done."
Custom CLI tools:
- Run
which <tool>or equivalent - If found → return tool name and path
- If not found → flag as
[TOOL-UNAVAILABLE]and suggest alternatives
Step 3 — Return Result
Return to calling skill:
tool: <tool-name>
category: <category>
status: available | needs-setup | unavailable
setup_instructions: <if needs-setup>
alternative: <if unavailable>
Gotchas
- Agent built-in tools (Read, Write, Grep, Bash) are ALWAYS available — don't waste time checking.
- MCP server availability varies by platform — what works in Claude Code may not work in Codex.
- A tool being installed globally doesn't mean it's available in the agent's sandbox.
- When called in batch by
process-decomposer, deduplicate — don't check the same tool twice.
Example
<examples> <example> <input>Find a tool for: "search the web for recent research papers"</input> <output> Tool: WebSearch Category: Web search Status: available (agent built-in) No setup needed. </output> </example> <example> <input>Find a tool for: "query a PostgreSQL database"</input> <output> Tool: PostgreSQL MCP server Category: MCP server Status: needs-setup Setup: Configure `mcp__postgres` in your MCP settings with connection string. See: https://github.com/modelcontextprotocol/servers/tree/main/src/postgres </output> </example> </examples>Impact Report
Tool lookup complete for: [requirement]
Tool: [name]
Status: available | needs-setup | unavailable
Platform: [current platform]
Related Skills
dvy1987/validate-skills
development
VerifiedTrustedCommunity
Run a fast, read-only health check across all skills in the library and produce a structured quality report — without modifying anything. Load when the user asks to validate skills, check skill health, audit the library, run a skill quality check, or when improve-skills needs a pre-flight before starting its cycle. Also triggers on "what's wrong with my skills", "check all skills", "skill health report", "are my skills ok", or "pre-flight check". Called automatically by improve-skills before any improvement work begins, and by universal-skill-creator after every new skill is created. Never modifies any file — only reads and reports.
2SKILL.mdUpdated Apr 16, 2026
dvy1987/universal-skill-creator
tools
VerifiedTrustedCommunity
Design, build, validate, and ship production-grade agent skills that work across OpenAI Codex, Ampcode, Factory.ai Droids, Google Gemini, Warp, Bolt.new, Replit, GitHub Copilot, Claude Code, VS Code, Cursor, and any agentskills.io compliant platform. Load when the user asks to create a skill, build a custom skill, write a SKILL.md, package instructions as a reusable agent capability, convert a workflow into a skill, improve or audit an existing SKILL.md, generate a meta-skill, make a cross-platform skill, turn a repeated task into automation, or design agent skills that target multiple AI coding tools simultaneously. Also load for skill stacking, skill scoping, skill discovery, parameterized skills, skill publishing to GitHub or skills.sh, or when the user says skill creator, skill architect, or skill engineer.
2SKILL.mdUpdated Apr 16, 2026
dvy1987/test-driven-development
development
VerifiedTrustedCommunity
Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.
2SKILL.mdUpdated Apr 16, 2026
dvy1987/technical-debt-audit
development
VerifiedTrustedCommunity
Audit the project's technical health and identify "high-interest" debt. Load when the user asks to check code quality, find TODOs, assess project health, or prepare for a refactoring sprint. Also triggers on "technical debt audit", "where is the code messy", "assess project health", "find my hacks", or "identify tech debt". Essential for maintaining velocity in growing projects.
2SKILL.mdUpdated Apr 16, 2026