validate-plugins

Validate Claude Code plugin manifests, marketplace entries, and repository structure.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill validate-plugins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-plugins
Source: https://github.com/shawn-sandy/agentic-acss-plugins/tree/main/.agents/skills/validate-plugins
Command: npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill validate-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps prevent broken Claude Code plugins from being published by verifying that manifests, marketplace entries, commands, and referenced skills all meet the expected structure and consistency rules.

Core Features & Use Cases

  • Validate plugin manifests and marketplace entries: Confirms required JSON fields exist and that marketplace entries follow conventions (including version-field rules).
  • Audit repository structure and cross-references: Ensures README, commands, and skills directories exist, and that command markdown files use the correct frontmatter and reference the SKILL.md logic rather than duplicating it.
  • Run deeper health reporting: Performs component reference checks, catalog parity checks, theme reference review, and validates bundled theme CSS using the repo’s theme validator.

Quick Start

Run the validation for all plugins in this repository by telling the agent: /validate-plugins --scope=all.

Frequently Asked Questions about validate-plugins

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Claude Code plugin structure before publishing to a marketplace?

You can validate Claude Code plugin structure by running checks that enforce manifest correctness, marketplace JSON conventions, required file presence, and SKILL.md reference consistency across the repository.

What does a repository health sweep for Claude Code plugins check?

A repository health sweep checks that README, commands, and skills directories exist, verifies command markdown files use correct YAML frontmatter, and ensures files reference SKILL.md logic rather than duplicating it.

Can I run deep per-plugin validation checks instead of a full repository sweep?

Yes, deep per-plugin validation checks support component reference checks, catalog parity validations, theme reference review, and bundled theme CSS validation using the repository's theme validator.

Does plugin manifest validation check version-field rules in marketplace entries?

Yes, plugin manifest validation confirms required JSON fields exist and verifies that marketplace entries follow conventions including specific version-field rules to prevent broken plugin publishing.

Why does my command markdown file fail plugin structure validation?

Command markdown files fail plugin structure validation when they lack correct YAML frontmatter or when they duplicate logic instead of referencing the SKILL.md file as required by the consistency rules.