tool-usage

Standardize tool and terminal selection for file operations and Git actions.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill tool-usage-grimlor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-usage
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/tool-usage
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill tool-usage-grimlor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents costly mistakes and inconsistent workflows by standardizing how an agent decides between VS Code/MCP tools and terminal commands for reads, edits, searches, tests, and Git actions.

Core Features & Use Cases

  • Tool-first routing rules: Directs the agent to use the specified tool for each task type, while avoiding unsafe terminal equivalents (e.g., no cat/sed/awk/echo, no grep/find, no raw git CLI).
  • Reliable test execution: Enforces running tests via the runTests tool only, with explicit prohibitions on terminal test commands like pytest, jest, or dotnet test.
  • Controlled script execution: Requires showing the script and asking the user to enable snippet execution tools before running code snippets (no terminal workaround running runtimes).
  • Verification after edits: Requires language-native lint/type checks after modifications, since editor Problems may miss issues.
  • Language-aware guidance via references: Uses dedicated references for Python, TypeScript, Java, and C# to choose the right checks and integrations.

Quick Start

Ask an AI to follow tool-usage rules for your request and it will select the correct tool for file edits and verification, run tests through runTests, and apply language-native lint/type gates using the appropriate reference guidance.

Frequently Asked Questions about tool-usage

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

FAQPage Schema
How do I ensure AI agents use VS Code tools instead of unsafe terminal commands for file edits and searches?

To ensure AI agents use VS Code tools instead of unsafe terminal commands, apply tool-first routing rules that prohibit shell equivalents like cat, sed, awk, echo, grep, and find. This standardization enforces safe tool-based interactions for file edits, searches, and Git operations.

Why should running tests via runTests override terminal commands like pytest or jest?

Running tests via runTests overrides terminal commands like pytest or jest to guarantee reliable test execution. Enforcing runTests-only testing prevents inconsistent workflows and avoids terminal test command workarounds during automated code verification.

How do I control script execution so AI agents do not run code snippets via terminal workarounds?

To control script execution and prevent terminal workarounds, require showing the script and asking the user to enable snippet execution tools. This controlled script execution approach stops agents from running code snippets directly through terminal runtimes.

What is the best way to standardize Git operations without using the raw git CLI?

The best way to standardize Git operations without the raw git CLI is to enforce tool-based interactions. Tool-first routing rules direct agents to use specified tools for Git actions, preventing costly mistakes from forbidden shell commands.

Does tool routing guidance support language-specific verification for Python and TypeScript?

Yes, tool routing guidance supports language-specific verification for Python and TypeScript. It uses dedicated references for Python, TypeScript, Java, and C# to choose the right checks and apply language-native lint and type gates after modifications.