tool-selection-strategy
Use this skill when deciding which tools to call in an agentic workflow. Always choose the minimal, most direct tool for each step and avoid redundant or speculative tool calls.
68
Quality
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Tool Selection Strategy
Principles:
- Least tool principle: Use the most specific, lightweight tool that accomplishes the goal.
- Read before writing: Always read a file before editing it to understand current state.
- Avoid speculative calls: Don't call a tool "just to see what happens". Have a clear hypothesis.
- Parallelize independent calls: If two reads don't depend on each other, fire them simultaneously.
Decision heuristic:
- Can I answer this from memory/context? No tool call needed.
- Is this a file operation? Use Read/Write/Edit tools.
- Is this a code search? Use Grep/Glob tools.
- Is this a system operation? Use Bash (last resort).
Anti-pattern: Using a heavy tool (Agent, Bash) when a lightweight dedicated tool suffices.
- Repository
- aiming-lab/MetaClaw
- Commit
922caf3
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.