Index of every page on this site: llms.txt
All skills
davila7 avatar

/agent-tool-builder

@053feb2
Run it yourself

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

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/agent-tool-builder

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈130 tokens for metadata: the name and description. ≈270 when used: this file.

Description uses 6.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈521 characters, or 6.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts20d5 checks · Risk SAFE
  • Gen Agent Trust Hub20d

    This skill is purely informational, providing guidelines and best practices for designing tools for AI agents. It does not contain any executable code, external dependencies, or security risks.

  • Socket20d

    No alerts

  • Snyk20d

    Risk: LOW · No issues

  • Runlayer9mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 053feb2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
metadata
{
  "source": "vibeship-spawner-skills (Apache 2.0)"
}

README badge

README badge for davila7/claude-code-templates/agent-tool-builder