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.
Source facts
- Repository
- aiming-lab/MetaClaw
- Last source activity
- March 10, 2026 at 18:04
- Detected SKILL.md language
- English
- Stars
- 3,456
- Forks
- 450
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- tool-selection-strategy
- description
- 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.
- category
- agentic
# 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:**
1. Can I answer this from memory/context? No tool call needed.
2. Is this a file operation? Use Read/Write/Edit tools.
3. Is this a code search? Use Grep/Glob tools.
4. Is this a system operation? Use Bash (last resort).
**Anti-pattern:** Using a heavy tool (Agent, Bash) when a lightweight dedicated tool suffices.
View on GitHub