/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 necessary. This skill covers tool design from schema to error handling. JSON Schema best
One skill from claude-code-templates.
shell
$ npx -y skills add davila7/claude-code-templates --skill agent-tool-builder --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/agent-tool-builder
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
Stats
Stars29,856
Forks3,189
LanguagePython
LicenseMIT
Ships with claude-code-templates
SKILL.md
agent-tool-builder.SKILL.md
--- 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 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" source: vibeship-spawner-skills (Apache 2.0) --- # 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
