Agent skill
tool-usage-discipline
Use skills for domain knowledge, MCP tools over manual lookups
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/tool-usage-discipline
SKILL.md
Skill: tool-usage-discipline
What I do
I ensure the most efficient and accurate use of available tools. I prioritise high-context MCP tools and loaded skills over manual exploration, preventing reinventing the wheel and reducing context bloat.
When to use me
- Before starting any investigation or code change
- To decide whether to use a specific MCP tool or a manual bash command
- When facing a large codebase where manual navigation is inefficient
- To optimise token usage and session length
Core principles
- Prioritise MCP — Use specialized tools (LSP, grep, glob) before generic ones (bash ls/cat).
- Consult skills first — Use loaded skills for domain expertise before seeking external information.
- Avoid redundancy — Don't call a tool if you already have the information in your context.
- Cache results — Store complex tool outputs (e.g. large grep results) in memory for the duration of the session.
Patterns & examples
Tool Selection Decision Matrix:
- Code Search: Use
greporast_grep(fast, indexed) over manualfind+cat. - Navigation: Use
lsp_goto_definitionover manual searching. - Verification: Use
lsp_diagnosticsbefore running a full build. - Domain Knowledge: Use the
skill()orvault-ragtools before web search.
Efficient Pattern:
- Inefficient:
ls -R,cat file1,cat file2,grep "pattern" file1... - Efficient:
grep -r "pattern"followed byreadon the most relevant match.
Anti-patterns to avoid
- ❌ Tool spam — Calling multiple tools to get information that a single, better tool could provide.
- ❌ Reinventing the tool — Writing a complex bash script when an MCP tool already handles that use case.
- ❌ Ignoring tool documentation — Using a tool sub-optimally because you haven't checked its parameters.
KB Reference
~/vaults/baphled/3. Resources/Knowledge Base/AI Development System/Skills/Workflow-Orchestration/Tool Usage Discipline.md
Related skills
pre-action— Deciding on the best tool approachmemory-keeper— Storing tool results to avoid repeat callsknowledge-base— Using specialized search toolstoken-efficiency— Optimising tool calls for token budget
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?