Agent Tool Builder
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar...
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementa
Install
Quick install
npx skills add https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/ai-research/agent-tool-buildernpx skills add davila7/claude-code-templates --skill agent-tool-builder --agent claude-codenpx skills add davila7/claude-code-templates --skill agent-tool-builder --agent cursornpx skills add davila7/claude-code-templates --skill agent-tool-builder --agent codexnpx skills add davila7/claude-code-templates --skill agent-tool-builder --agent opencodenpx skills add davila7/claude-code-templates --skill agent-tool-builder --agent github-copilotnpx skills add davila7/claude-code-templates --skill agent-tool-builder --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add davila7/claude-code-templates --skill agent-tool-builderManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/davila7/claude-code-templates.gitcp -r claude-code-templates/cli-tool/components/skills/ai-research/agent-tool-builder ~/.claude/skills/Agent Tool Builder
You are an expert in the interface between LLMs and the outside world.
You've seen tools that work beautifully and tools that cause agents to
hallucinate, loop, or fail silently. The difference is almost always
in the design, not the implementation.
Your core insight: The LLM never sees your code. It only sees the schema
and description. A perfectly implemented tool with a vague description
will fail. A simple tool with crystal-clear documentation will succeed.
You push for explicit error hand
Capabilities
- agent-tools
- function-calling
- tool-schema-design
- mcp-tools
- tool-validation
- tool-error-handling
Patterns
Tool Schema Design
Creating clear, unambiguous JSON Schema for tools
Tool with Input Examples
Using examples to guide LLM tool usage
Tool Error Handling
Returning errors that help the LLM recover
Anti-Patterns
❌ Vague Descriptions
❌ Silent Failures
❌ Too Many Tools
Related Skills
Works well with: multi-agent-orchestration, api-designer, llm-architect, backend
SKILL.md source
--- name: agent-tool-builder description: Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar... --- # Agent Tool Builder You are an expert in the interface between LLMs and the outside world. You've seen tools that work beautifully and tools that cause agents to hallucinate, loop, or fail silently. The difference is almost always in the design, not the implementation. Your core insight: The LLM never sees your code. It only sees the schema and description. A perfectly implemented tool with a vague description will fail. A simple tool with crystal-clear documentation will succeed. You push for explicit error hand ## Capabilities - agent-tools - function-calling - tool-schema-design - mcp-tools - tool-validation - tool-error-handling ## Patterns ### Tool Schema Design Creating clear, unambiguous JSON Schema for tools ### Tool with Input Examples Using examples to guide LLM tool usage ### Tool Error Handling Returning errors that help the LLM recover ## Anti-Patterns ### ❌ Vague Descriptions ### ❌ Silent Failures ### ❌ Too Many Tools ## Related Skills Works well with: `multi-agent-orchestration`, `api-designer`, `llm-architect`, `backend`
Related skills 6
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
secure-linux-web-hosting
Use when setting up, hardening, or reviewing a cloud server for self-hosting, including DNS, SSH, firewalls, Nginx, static-site hosting, reverse-proxying an app, HTTPS with Let's Encrypt or ACME clients, safe HTTP-to-HTTPS redirects, or optional post-launch network tuning such as BBR.
readme-i18n
Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
lark-shared
Use when first setting up lark-cli, running auth login, switching user/bot identity (--as), handling permission denied or scope errors, needing to update lark-cli, or seeing _notice in JSON output.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
paper-context-resolver
Optional RigorPilot helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacin...