playbook-cli-audit

Solid

Audit all packmind-* skills for CLI compatibility issues: deprecated commands, invalid options, wrong file formats, missing flags, and version mismatches against the locally installed Packmind CLI. Use when you want to check that skills referencing packmind-cli are up to date, after a CLI upgrade, before a release, or whenever you suspect skills may reference outdated CLI commands. Also triggers on phrases like "audit CLI usage", "check skills for CLI issues", "are my skills up to date with the CLI", or "CLI compatibility check".

AI & Automation 287 stars 14 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 85/100

Stars 20%
82
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Playbook CLI Audit Detect incompatibilities between the packmind-* skills deployed in `.claude/skills/` and the current Packmind CLI. Skills evolve independently from the CLI — when the CLI deprecates or removes commands, renames flags, or changes accepted file formats, skills can silently break. This audit catches those issues before users hit them at runtime. **This skill only detects issues — it does not fix them.** ## Phase 1: Establish CLI Surface Build the authoritative map of what the CLI currently supports. ### 1.1 Get CLI version ```bash node ./dist/apps/cli/main.cjs --version ``` Remember this as `$CLI_VERSION` (e.g., `0.26.0`). If the command fails, try `packmind-cli --version` as a fallback. If both fail, stop and tell the user the CLI is not available. ### 1.2 Build the command map from CLI source code The CLI command definitions live in `apps/cli/src/infra/commands/`. Read the command registration files to build a complete map of: - **Available top-level commands** and their subcommands - **Accepted options/flags** for each command (names, types, whether required) - **Accepted argument types** (file paths, strings, etc.) and any format constraints - **Deprecated commands** — look for `[Deprecated]` in descriptions and `has been removed` in handler code - **Migration paths** — what the deprecated command's error message suggests instead Structure this internally as a reference table. Here is the expected shape — adapt if the source reveals more or fe...

Details

Author
PackmindHub
Repository
PackmindHub/packmind
Created
8 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

playbook-audit

Audit deployed Packmind playbook artifacts for contradictions, duplications, and coverage gaps. Produces `playbook-audit-report.md` at project root. Use after bulk artifact updates, before onboarding, or on a regular cadence.

287 Updated today
PackmindHub
AI & Automation Listed

cli-ux-audit

Audit any CLI tool for terminal user experience — help text, command structure, error messages, output formatting, discoverability, and accessibility — produces a scored report with actionable fixes

3 Updated today
anthril
AI & Automation Solid

plugin-audit

Comprehensive audit pipeline for skills, plugins, agents, and commands. Validates structure, quality, security, marketplace compliance, cross-platform compatibility, and ecosystem integration. Runs all built-in validation tools, invokes domain-appropriate agents for code review, and produces a pass/fail gate report. Usage: /plugin-audit <skill-path>

16,782 Updated 3 days ago
alirezarezvani
AI & Automation Listed

do-skills-audit

Audit all Claude Code skills for compliance with canonical template standards. Use when checking skill quality, validating skill structure, linting SKILL.md files, verifying frontmatter, or scanning for skill issues. Runs deterministic validation rules and best practices sync against latest Anthropic docs by default.

14 Updated today
tomcounsell
Data & Documents Solid

skillshare-codebase-audit

Cross-validate CLI flags, docs, tests, and targets for consistency across the codebase. Use this skill whenever the user asks to: audit the codebase, check for consistency issues, find undocumented flags, verify test coverage, validate targets.yaml, check handler split conventions, or verify oplog instrumentation. This is a read-only audit — it reports issues but never modifies files. Use after large refactors, before releases, or whenever you suspect docs/code/tests have drifted out of sync.

2,096 Updated today
runkids