which-tool_skill

Overview

This skill helps choose the best CLI tool for a given task, provide graceful fallbacks, and trigger research when tools underperform. It focuses on file search, content search, JSON processing, and other common developer CLI needs. The goal is faster, more ergonomic commands while never blocking the workflow.

How this skill works

On first use in a session it runs a detection script to list available modern tools, missing candidates, and system context (OS, package managers). It maps the task to a preferred tool using a curated selection table, uses fallbacks or legacy commands when needed, and surfaces installation suggestions or research prompts when gains are significant. Results are cached per session to avoid repeated detection runs.

When to use it

• Choosing which CLI tool for file search, content search, JSON processing, or HTTP requests
• When a tool feels unexpectedly slow for the task size
• If you express frustration with the current tool or workflow
• When a task could be done more elegantly with a specialized CLI
• Before recommending a tool, to verify availability on the system

Best practices

• Always run detection before recommending a specific tool; cache results per session
• Prefer modern tools (fd, rg, jq, bat, delta, etc.) with optimal flags
• Provide a non-blocking fallback and surface install suggestions for significant improvements
• Trigger research when a tool is 3x+ slower than expected or lacks critical features
• Avoid recommending unmaintained tools and never assume an unverified tool is installed

Example use cases

• Find files by name: prefer fd, fallback to find; fd -e yaml -e yml
• Search file contents: prefer rg (respects .gitignore) — e.g. rg "authentication" --type ts --type js
• Process JSON: prefer jq; if missing, use node/python with a suggestion to install jq
• View files with syntax highlighting: prefer bat instead of cat
• Navigate directories quickly: prefer zoxide for frecency-based jumping