plugin-audit_skill

This skill audits Claude Code plugins against the latest changelog, validating structure, detecting deprecations, and recommending best practices for release
  • Python

19

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 greyhaven-ai/claude-code-config --skill plugin-audit

  • SKILL.md1.8 KB

Overview

This skill performs a thorough audit of Claude Code plugins and skills to validate structure, detect deprecated patterns, and recommend concrete changes based on the latest changelog. It returns a prioritized checklist, a quality score, and actionable remediation steps to prepare plugins for release or compatibility with recent Claude Code versions. Use it to harden plugins, reduce deprecations, and align with current best practices.

How this skill works

The auditor inspects repository layout, required files, and frontmatter fields, then cross-references patterns against a curated deprecation checklist and changelog feature matrix. It flags structural issues, insecure or dangerous patterns, and missing modern features, and produces a remediation report with examples and priority levels. The output includes a noteable-items list, recommended edits, and a final quality score for release readiness.

When to use it

  • Before releasing or publishing a Claude Code plugin or skill
  • When upgrading to a new Claude Code version or changelog milestone
  • During code reviews to catch deprecated patterns early
  • To validate frontmatter and metadata for agents, skills, and commands
  • When performing a security or compatibility sweep across multiple plugins

Best practices

  • Maintain canonical directory layout and include all required entry files and metadata
  • Keep frontmatter concise, complete, and validated against the latest schema
  • Replace deprecated patterns listed in the changelog with supported alternatives as early as possible
  • Adopt new changelog features incrementally and include tests or examples demonstrating them
  • Document risky tool usage and add clear guardrails or usage limits to reduce security exposure

Example use cases

  • Generate a pre-release audit report that lists deprecated fields and exact replacements
  • Validate agent and command frontmatter across a mono-repo to ensure consistent metadata
  • Run a security-focused pass to detect tool injection patterns and unsafe subprocess or eval usage
  • Produce a remediation checklist for maintainers with line-level examples and suggested commits
  • Score a portfolio of plugins and prioritize updates by impact and difficulty

FAQ

A prioritized checklist, line-level warnings, suggested code or frontmatter edits, a changelog-mapped deprecation list, and a final quality score.

Can this detect security issues?

Yes. The audit flags dangerous patterns, improper tool restrictions, and insecure defaults, and gives remediation steps to mitigate risk.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational