Agent Tool Contracts

Design agent/CLI tool schemas, naming, errors, and idempotency for LLM callers.

Autor: charlieviettq · charlieviettq/awesome-agent-skill

Testowano · Działa ★ 9.2/10

Agent Tool Contracts — Design agent/CLI tool schemas, naming, errors, and idempotency for LLM callers.

Co robi ten skill

Provides concrete rules and a review checklist for designing tools, parameter schemas, and CLI surfaces meant to be called by LLM agents: verb-noun naming, minimal required parameters, explicit side-effect wording, bounded/paginated output, stable {code,message} errors, and an idempotency pattern table for read/create/update/delete. Triggers when the user is defining tools for agents, SDKs, MCP servers, or AI-native CLIs.

Raport z testu

Applying its idempotency table to a `delete_project` tool turned a bare 'delete and return success' baseline into a two-step confirm + soft-delete design with a stable NOT_FOUND/CONFIRMATION_REQUIRED error schema — a concrete, checklist-driven improvement over default output.

Testowano: 2026-07-15 · Claude Code 2.x (agent harness)

Instalacja

git clone https://github.com/charlieviettq/awesome-agent-skill
mkdir -p ~/.claude/skills
cp -r awesome-agent-skill/.claude/skills/agent-tool-contracts ~/.claude/skills/agent-tool-contracts

Komendy i przykładowe prompty

  • /agent-tool-contractsDesign agent/CLI tool schemas, naming, errors, and idempotency for LLM callers.

Skille uruchamiają się na zwykłe polecenia — bez komend do zapamiętania. Po instalacji aktywują go prompty takie jak te (po angielsku):

  • Help me design the parameter schema for a new MCP tool that creates PRs
  • Review this CLI's argument names and exit codes for AI agent compatibility
  • What's the best idempotency pattern for an agent-facing delete tool?