How do I install the CLI Tools skill?

Run npx skillmds@latest add netresearch/cli-tools in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CLI Tools safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CLI Tools?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CLI Tools free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under (MIT AND CC-BY-SA-4.

Who published CLI Tools?

netresearch (@netresearch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CLI Tools by netresearch — Agent Skill

Name: CLI Tools
Rating: 4.2 (5 reviews)
Author: netresearch

CLI Tools

Use when ANY command fails with 'command not found', when installing CLI tools (ripgrep, fd, jq, yq, bat, etc.), auditing project environments, or batch-updating tools. Triggers on: command not found, install tool, missing binary, environment audit, update tools, which, apt install, brew install.

netresearch Updated Sep 17, 2026

File contents

CLI Tools Skill

Install, audit, update, and recommend CLI tools across 77 cataloged entries.

Triggers

Reactive: command not found errors -- auto-resolve
Proactive: "check environment", "install X", "update tools"
Advisory: Recommend modern alternatives (grep->rg, find->fd, JSON->jq)

Preferred Modern Tools

Recommend over legacy equivalents. See references/preferred-tools.md for examples.

Legacy	Modern	Legacy	Modern
`grep -r`	`rg`	`diff`	`difft`
`find`	`fd`	`time`	`hyperfine`
grep on JSON	`jq`	`cat`	`bat`
sed on YAML	`yq`	`cloc`	`tokei`/`scc`
awk on CSV	`qsv`	grep for sec	`semgrep`
sed on TOML	`dasel`

Workflows

Missing Tool Resolution

Diagnose: which <tool>, command -v <tool>, type -a <tool>
Map binary: Check references/binary_to_tool_map.md (rg->ripgrep, ansible->ansible-core, batcat->bat)
Install: scripts/install_tool.sh <tool> install
Verify: which <tool> + <tool> --version; if still missing: hash -r, check PATH

See references/resolution-workflow.md for full diagnostic steps.

Environment Audit

Run scripts/check_environment.sh audit . and scripts/detect_project_type.sh, then cross-reference with references/project_type_requirements.md for per-type tool lists.

Batch Update

scripts/auto_update.sh (all managers) or scripts/install_tool.sh <tool> update (single).

Troubleshooting

Symptom	Fix
Installed but not found	`hash -r` or add dir to PATH
No sudo	`cargo install`, `pip install --user`, manual binary; on Debian/Ubuntu `apt-get download` + `dpkg -x`
Debian `bat`=`batcat`, `fd`=`fdfind`	Symlink to `~/.local/bin/`

See references/troubleshooting.md for Docker fallbacks and permission workarounds.

Scripts

Script	Purpose
`scripts/install_tool.sh`	Install/update/uninstall/status
`scripts/auto_update.sh`	Batch update package managers
`scripts/check_environment.sh`	Audit environment and PATH
`scripts/detect_project_type.sh`	Detect project type

References

File	Purpose
`references/binary_to_tool_map.md`	Binary-to-catalog mapping
`references/project_type_requirements.md`	Tools per project type
`references/preferred-tools.md`	Modern tool usage patterns
`references/resolution-workflow.md`	Diagnostic/install/verify flow
`references/troubleshooting.md`	PATH, permissions, fallbacks

---name: cli-toolsdescription: Use when ANY command fails with 'command not found', when installing CLI tools (ripgrep, fd, jq, yq, bat, etc.), auditing project environments, or batch-updating tools. Triggers on: command not found, install tool, missing binary, environment audit, update tools, which, apt install, brew install.license: (MIT AND CC-BY-SA-4.0)---# CLI Tools SkillInstall, audit, update, and recommend CLI tools across 77 cataloged entries.## Triggers- **Reactive**: `command not found` errors -- auto-resolve- **Proactive**: "check environment", "install X", "update tools"- **Advisory**: Recommend modern alternatives (`grep`->`rg`, `find`->`fd`, JSON->`jq`)## Preferred Modern ToolsRecommend over legacy equivalents. See `references/preferred-tools.md` for examples.| Legacy | Modern | Legacy | Modern ||--------|--------|--------|--------|| `grep -r` | `rg` | `diff` | `difft` || `find` | `fd` | `time` | `hyperfine` || grep on JSON | `jq` | `cat` | `bat` || sed on YAML | `yq` | `cloc` | `tokei`/`scc` || awk on CSV | `qsv` | grep for sec | `semgrep` || sed on TOML | `dasel` | | |## Workflows### Missing Tool Resolution1. **Diagnose**: `which <tool>`, `command -v <tool>`, `type -a <tool>`2. **Map binary**: Check `references/binary_to_tool_map.md` (`rg`->`ripgrep`, `ansible`->`ansible-core`, `batcat`->`bat`)3. **Install**: `scripts/install_tool.sh <tool> install`4. **Verify**: `which <tool>` + `<tool> --version`; if still missing: `hash -r`, check PATHSee `references/resolution-workflow.md` for full diagnostic steps.### Environment AuditRun `scripts/check_environment.sh audit .` and `scripts/detect_project_type.sh`, then cross-reference with `references/project_type_requirements.md` for per-type tool lists.### Batch Update`scripts/auto_update.sh` (all managers) or `scripts/install_tool.sh <tool> update` (single).## Troubleshooting| Symptom | Fix ||---------|-----|| Installed but not found | `hash -r` or add dir to PATH || No sudo | `cargo install`, `pip install --user`, manual binary; on Debian/Ubuntu `apt-get download` + `dpkg -x` || Debian `bat`=`batcat`, `fd`=`fdfind` | Symlink to `~/.local/bin/` |See `references/troubleshooting.md` for Docker fallbacks and permission workarounds.## Scripts| Script | Purpose ||--------|---------|| `scripts/install_tool.sh` | Install/update/uninstall/status || `scripts/auto_update.sh` | Batch update package managers || `scripts/check_environment.sh` | Audit environment and PATH || `scripts/detect_project_type.sh` | Detect project type |## References| File | Purpose ||------|---------|| `references/binary_to_tool_map.md` | Binary-to-catalog mapping || `references/project_type_requirements.md` | Tools per project type || `references/preferred-tools.md` | Modern tool usage patterns || `references/resolution-workflow.md` | Diagnostic/install/verify flow || `references/troubleshooting.md` | PATH, permissions, fallbacks |

Frequently asked questions