CLI Audit

Audit an existing CLI against cli-build: how well an agent can operate it and how well a human can read it. Use when the user wants to audit a CLI, check whether a tool is agent-first, find out what a published CLI got wrong, grade a CLI's human output, verify that named safety features are actually wired, or prepare a patch list before improving an existing command-line tool. Reports findings with evidence; it does not patch.

115 stars 15 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add crafter-station/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add crafter-station/skills --skill cli-audit
Manual install
git clone --depth 1 https://github.com/crafter-station/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/cli-audit ~/.claude/skills/cli-audit

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# cli-audit

Audit a CLI that already exists against the rules in `cli-build`. The output is a findings list with evidence, not a score.

`cli-build` builds. This reads what was built and says where it drifted from what it claims.

## Why there is no score

The founding case of `cli-build`'s `human-output.md` is a CLI that **passed every mechanical gate and was unreadable**: 275 rows for someone who asked what was playing that evening, a percentage that read backwards, one title repeated fourteen times. No gate failed.

A number over that CLI would have read as healthy. That is the exact failure this skill exists to avoid, so it produces no number. A run yields three streams and they never merge:

| Layer | Decided by | Output |
|---|---|---|
| Deterministic | `scripts/audit.sh` | `PASS` / `FAIL` / `NA` / `SKIP` per check, with the evidence inline |
| Semi | script produces evidence, you read the verdict | finding or cleared, with the evidence quoted |
| Judgment | you, reading real output | finding or cleared, with the output pasted |

**A clean deterministic run is not a clean CLI.** Say that in the report every time, because the reader will otherwise take the passes as the answer.
Read the full skill on GitHub

Details

Skill name
cli-audit
Path
skills/cli-audit/SKILL.md
License
MIT
Repo updated
7 September 2026

FAQ

What does the CLI Audit skill do?

Audit an existing CLI against cli-build: how well an agent can operate it and how well a human can read it. Use when the user wants to audit a CLI, check whether a tool is agent-first, find out what a published CLI got wrong, grade a CLI's human output, verify that named safety features are actually wired, or prepare a patch list before improving an existing command-line tool. Reports findings with evidence; it does not patch.

How do I install the CLI Audit skill?

Claude Code plugin: /plugin marketplace add crafter-station/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is CLI Audit popular?

It lives in crafter-station/skills, which has 115 GitHub stars and 15 forks.

Related skills

Obsidian Plugin Release

115

crafter-station/skills

Release a new version of an Obsidian community plugin without forgetting steps. Use when: (1) user says "release the plugin", "bump <plugin> to X.Y.Z", "ship a new Obsidian release", "tag a new plugin version", "publish to the obsidian directory", (2) the working directory contains manifest.json + main.js + versions.json (Obsidian plugin signature), (3) user wants to scaffold the release workflow into an existing plugin (`scaffold-workflow` arg). Handles version bump across manifest.json + package.json + versions.json, build, lint, conventional commit, signed annotated tag, push, and lets the

Productivity & Notes15

CLI Build

115

crafter-station/skills

Design and build a CLI that an AI agent can operate safely and a human can supervise. Use when the user wants to build a CLI, wrap an API in a command-line tool, build a CRUD or local-first tool over a database or filesystem the user already owns, add --json or --dry-run to an existing CLI, design a trust ladder or approval gate for risky commands, wrap an async API so agents do not write their own poll loop, or decide how to distribute a CLI (npm, native binary, source). Runs on its own when the contract is yours to define; follows a surface-recon report when the target is someone else's serv

Software Development15

Generate Brand Assets

115

crafter-station/skills

Generate OG images and favicon based on project branding. Use when: (1) user needs social media preview images for their project, (2) user wants to generate a favicon, (3) user is setting up branding assets for a website or app, (4) user has brand colors and wants professional-looking Open Graph images. Automatically generates correctly sized images optimized for social platforms (Twitter, LinkedIn, Facebook) and favicon formats.

Frontend & Design15

Trace Requirement

292

danielvm-git/bigpowers

Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests. Produces specs/TRACEABILITY_LATEST.md. Use when you want to verify coverage of a release plan, audit which stories are implemented, or find "dark" stories with no code.

Software Development23

Supply Chain Audit

115

crafter-station/skills

Read-only audit of a developer machine for npm/PyPI supply-chain compromise. Checks for known IOCs from the 2025-2026 wave — Shai-Hulud 2.0 (Nov 2025), Mini Shai-Hulud / TeamPCP (May 2026), Axios DPRK (Mar 2026), Shai-Hulud 3.0 / keyv-cacheable (Aug 2026), and any future campaigns added to the IOC pack. Scans persistence artifacts (LaunchAgent / systemd unit / Windows Run key / gh-token-monitor / .claude and .vscode droppers), payload files (router_init.js, setup_bun.js, bun_environment.js, Math_Symbol.js, math_init.js), compromised package versions in every node_modules under the user's proje

Software Development15

Request Review

292

danielvm-git/bigpowers

Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.

Software Development23

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.