effective-tool-use

Enforce tool selection and execution rules for coding workflows.

3|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/bhaumikmaan/claude-code-master-skills --skill effective-tool-use
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effective-tool-use
Source: https://github.com/bhaumikmaan/claude-code-master-skills/tree/main/skills/effective-tool-use
Command: npx skills add https://github.com/bhaumikmaan/claude-code-master-skills --skill effective-tool-use

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents costly tool misuse, token waste, unsafe git actions, and context exhaustion by prescribing when and how to use IDE tools, shell commands, and background tasks in coding workflows.

Core Features & Use Cases

  • Tool preference matrix: choose dedicated IDE tools for find, read, edit, and write operations instead of shell equivalents to preserve diffs and permissions.
  • Token cost hierarchy: enforce Glob → Grep → Read to minimize tokens and only read full files when necessary, and spawn subagents for large multi-file research.
  • Execution and git safety: guidance on parallel vs sequential execution, sandbox awareness, file-path hygiene, commit practices, and never force-pushing or skipping hooks unless explicitly requested.
  • Use Case: safely prepare changes by locating relevant files with Glob, preview matches with Grep, read minimal ranges, propose edits, and stage and commit specific files without risking destructive git commands.

Quick Start

Inspect the repository using Glob then Grep before reading files, prefer IDE tools over shell commands, and propose safe git commands for staging and committing my changes.

Frequently Asked Questions about effective-tool-use

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I minimize token usage when reading and searching files in a large codebase?

To minimize token usage when searching files, enforce a Glob → Grep → Read cost hierarchy to locate relevant files and preview matches, only reading full files or minimal ranges when truly necessary.

What is the best way to safely stage and commit changes with git?

The best way to safely commit changes with git is to propose safe git commands for staging specific files, avoiding destructive git commands, and never force-pushing or skipping hooks unless explicitly requested.

Should I use IDE tools or shell commands for file operations?

You should use dedicated IDE tools for find, read, edit, and write file operations instead of shell equivalents to preserve diffs and maintain file permissions within your coding workflow.

How do I handle sandboxed environments and background tasks when executing commands?

To handle sandboxed environments, maintain sandbox-aware file paths, explicitly manage background tasks, and choose between parallel versus sequential command execution based on the specific coding task requirements.

Why should I read files before editing, and how do I manage large multi-file research?

You should follow read-before-edit rules to prevent context exhaustion, and for large multi-file research, you should spawn subagents to handle the investigation efficiently without wasting tokens.