tool-use-patterns
Skill106 starsChanged 7 months agoMITView on GitHub
Patterns for Claude tool use including sequential tools, parallel execution, error handling, and agentic loops.
In this repository13 other files it gives its agents.
- dashboard/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dashboard/CLAUDE.mdCLAUDE.md
- business-news-monitorSkill
- claude-api-helperSkill
- commsSkill
- cron-managementSkill
- idea-groomingSkill
- mcp-integrationSkill
- multi-perspective-grillingSkill
- prompt-engineeringSkill
- Task SystemSkill
- web-researchSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Keep tool descriptions concise but complete
- Distinctive: line 45
Use is_error for graceful failure handling
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tool Use Patterns
Advanced patterns for Claude's tool use capability.
Agentic Loop
while True:
response = client.messages.create(
model="claude-sonnet-4-20250514",
tools=tools,
messages=messages
)
if response.stop_reason == "end_turn":
break
for block in response.content:
if block.type == "tool_use":
result = execute_tool(block.name, block.input)
messages.append({"role": "assistant", "content": response.content})
messages.append({"role": "user", "content": [
{"type": "tool_result", "tool_use_id": block.id, "content": str(result)}
]})Error Handling
{"type": "tool_result", "tool_use_id": id, "is_error": true, "content": "File not found"}Parallel Tool Calls
Claude can request multiple tools in one response. Execute them concurrently and return all results.
Best Practices
- Keep tool descriptions concise but complete
- Include parameter constraints in the schema
- Return structured data from tools when possible
- Use is_error for graceful failure handling
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

