playbook-audit

Solid

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.

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 Audit Detect contradictions, duplications, and broken cross-references between playbook artifacts (standards, commands, skills) deployed in `.claude/` directories. Produces a structured `playbook-audit-report.md` at the project root. **This skill only detects issues — it does not fix them.** ## Phase 1: Discover Artifacts Before launching any sub-agents, build an artifact inventory by scanning `.claude/` directories: ### 1. Standards Glob `.claude/rules/**/*.md` to find all standard files. For each file: - Extract YAML frontmatter fields: `name`, `paths`, `alwaysApply`, `description` - Extract the body content (everything after the frontmatter closing `---`) - If frontmatter is malformed, log a WARNING and use the filename as the name ### 2. Commands Glob `.claude/commands/**/*.md` to find all command files. For each file: - Extract YAML frontmatter field: `description` - Extract the body content - If frontmatter is malformed, log a WARNING and use the filename as the name ### 3. Skills Glob `.claude/skills/*/SKILL.md` to find all skill entry points. For each skill directory: - Extract YAML frontmatter fields from SKILL.md: `name`, `description` - Extract the SKILL.md body content - Glob `references/*.md` and `scripts/*` within the skill directory — include a one-line summary of each - If a skill directory exists but has no SKILL.md, flag as an INFO finding ### 4. Compile Artifact Inventory Build a markdown document structured as: ``` ## Artifact Inven...

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-cli-audit

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".

287 Updated today
PackmindHub
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

claude-audit

Audit a project's effective Claude Code configuration — custom and plugin-provided agents and skills — and produce a structured overlap/conflict report with keep / modify / drop recommendations scoped to the project's stated objectives. Trigger this skill whenever the user types `/claude-audit`, asks to "audit my claude config", "find overlap in my agents", "check for skill conflicts", "are any of my agents duplicates", "what's redundant in my setup", or any similar request to review the agent/skill surface for the current project. Also trigger after a fresh plugin install when the user wants to verify nothing new collides with what's already there.

1 Updated yesterday
glitchwerks
AI & Automation Solid

doc-audit

Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage. Produces a structured markdown report at project root. Use when docs may have drifted from the codebase, before a release, or on a regular cadence.

287 Updated today
PackmindHub
AI & Automation Solid

packmind-update-playbook

Use when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills). Triggers on explicit phrases like "update packmind standard", "add a packmind skill", "fix packmind command", "change packmind playbook", "deprecate a standard". Also triggers — even without an explicit request — whenever the conversation reveals an opportunity: a new coding convention was just agreed on, a recurring pattern emerged, a workflow changed, a rule was found outdated, or the user says things like "we always do X", "let us remember to Y", "that is the pattern we use". If there is any chance the conversation established a convention or exposed a gap, invoke this skill proactively. This skill defines a mandatory workflow: do NOT edit artifact files directly — follow all phases regardless of change size.

287 Updated today
PackmindHub