Command

/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,

One command from claude-skills.

shell

$ npx -y skills add alirezarezvani/claude-skills --agent claude-code

Ships with claude-skills. Installing the plugin gets this command.

How it fires

How this command gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/plugin-audit

Context preview

What this command does when you run it.

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,

Stats

Stars23,062

Forks3,139

LanguagePython

LicenseMIT

Ships with claude-skills

Command definition

plugin-audit.md

---
name: plugin-audit
description: |
  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>
argument-hint: "<skill-path>"
---

# /plugin-audit

Full audit pipeline for any skill, plugin, agent, or command in this repository. Runs 8 validation phases, auto-fixes what it can, and only stops for user input on critical decisions (breaking changes, new dependencies).

## Usage

```bash
/plugin-audit product-team/code-to-prd
/plugin-audit engineering/agenthub
/plugin-audit engineering-team/playwright-pro
```

## What It Does

Execute all 8 phases sequentially. Stop on critical failures. Auto-fix non-critical issues. Report results at the end.

---

## Phase 1: Discovery

Identify what the skill contains and classify it.

1. Verify `{skill_path}` exists and contains `SKILL.md`
2. Read `SKILL.md` frontmatter — extract `name`, `description`, `Category`, `Tier`