| name | Tool Coach |
| description | Use automatically for Claude Code work involving files, tools, bash, edits, tests, long commands, failed tool calls, or unfamiliar repos. Improves tool choice, prevents loops, and keeps work high-quality without adding broad context. |
| allowed-tools | Read, Bash |
Tool Coach
Use this skill to choose tools deliberately and avoid wasteful or unsafe loops.
Tool Discipline
- Use
Bash with rg, rg --files, or find before broad reads.
- Use
Read before Edit/MultiEdit.
- Use
Edit for small precise changes; MultiEdit for several edits in one file; Write only for new files or full rewrites.
- Use
Bash for targeted verification, not blind full-suite runs unless needed.
- Never paste huge logs. Use
tail, filters, or targeted rg/grep.
- If a command fails twice, stop and diagnose root cause. Do not loop.
- For long commands, state command, expected signal, timeout/log path, and next check.
- For unfamiliar repo work, call or follow Context Intelligence first.
- For UI work, run Premium UI review before final.
- For release-risk work, call Test Strategy and Security Hardening.
Tool and MCP Selection
When MCP servers are available, prefer the official/current server for the target service over recreating the integration through ad hoc web fetches. Use MCP for service-native context such as GitHub, databases, observability, or issue trackers when it is authenticated and relevant. Do not use MCP for local filesystem work that the current host tools already handle better. If MCP auth is missing, state that clearly and continue with safe local evidence.
Tool Names
This LTS uses Bash for search because some Claude Code sessions do not expose direct Grep/Glob tools. For text search, call Bash with rg or command-line grep. For file discovery, call Bash with rg --files or find. Never emit tool_use.name = "Grep", tool_use.name = "Glob", tool_use.name = "grep", or tool_use.name = "glob".
Long Command Pattern
Prefer:
mkdir -p /tmp/claude-lts-jobs
command > /tmp/claude-lts-jobs/<name>.log 2>&1 &
echo $!
Then check:
ps -p <pid> -o pid,etime,command
tail -n 80 /tmp/claude-lts-jobs/<name>.log
Use this only when background execution is actually useful. Otherwise run normally and wait.
Quality Rule
Do not reduce correctness, tests, or security to save tokens. Reduce waste by narrowing context and running focused checks.
