cli-tools_skill

This skill manages CLI tool installation, environment auditing, and automated updates to keep projects running smoothly.
  • Python

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill questnova502/claude-skills-sync --skill cli-tools

  • SKILL.md1.5 KB

Overview

This skill manages CLI tool installation, environment auditing, and routine updates to keep developer workstations and CI runners consistent. It reacts to missing-command errors, proactively audits project environments, and runs batch maintenance for managed tools. Built to streamline recovery from 'command not found' failures and to enforce tool-version requirements across projects.

How this skill works

When a shell reports a missing binary, the skill extracts the binary name, maps it to a known tool in the catalog, and invokes the install script to add the missing package. For proactive checks, it runs an environment audit that detects project type, compares required tools and versions against a catalog, and reports gaps or outdated tools. Maintenance workflows call batch update scripts that update package managers and installed tools consistently.

When to use it

  • A shell returns 'bash: <tool>: command not found' during development or CI
  • You want to audit a repository to see which CLI tools are required or missing
  • Preparing a new developer machine or CI runner to ensure all tools are installed
  • After pulling changes that add new tooling or change required versions
  • Running periodic maintenance to update or reconcile installed tools

Best practices

  • Keep the binary-to-tool mapping current so automatic resolution is accurate
  • Run environment audits as part of pre-commit checks or CI pipelines
  • Prefer non-interactive installs in CI and explicit version pins for reproducibility
  • Review install logs and retry failing installs with the same environment context
  • Use the detect-project-type step to limit audits to relevant toolsets

Example use cases

  • Auto-installing ripgrep when a developer types 'rg' and it is missing
  • Scanning a monorepo to list required language runtimes and package managers
  • Preparing a container image by auditing and installing only necessary CLI tools
  • Scheduling nightly maintenance to update package managers and apply tool upgrades
  • Recovering a CI job that failed due to an uninstalled linter or formatter

FAQ

The skill automates installs but is intended to run in controlled contexts; configure it for interactive confirmation or non-interactive CI mode depending on environment.

How does it determine which package manager to use?

It uses project detection and a catalog mapping to select the appropriate installer for the tool and environment (e.g., apt, brew, npm, pip).

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
cli-tools skill by questnova502/claude-skills-sync | VeilStrat