plugin-validator

Validate Claude Code plugin directories for structure, manifest conformance, and dependencies.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/VanLengs/astra-studio-plugins --skill plugin-validator-vanlengs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-validator
Source: https://github.com/VanLengs/astra-studio-plugins/tree/main/studio-quality/skills/plugin-validator
Command: npx skills add https://github.com/VanLengs/astra-studio-plugins --skill plugin-validator-vanlengs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validates a Claude Code plugin directory for structural correctness, manifest compliance, skill quality, and dependency integrity, returning a detailed diagnostic report with remediation steps.

Core Features & Use Cases

  • Structural validation of manifests, required fields, and directory layout
  • Per-skill validation including SKILL.md quality checks and naming consistency
  • Dependency integrity checks across MCPs and inter-skill references
  • Comprehensive diagnostic reporting with prioritized remediation
  • Optional status updates to studio change workspaces when applicable

Quick Start

Run the plugin validator on your plugin directory to generate a comprehensive diagnostic report.

Frequently Asked Questions about plugin-validator

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

FAQPage Schema
How do I validate a Claude Code plugin directory before packaging?▼

To validate a plugin, run the validator on your completed plugin directory to check structural integrity, manifest conformance, and dependency health, producing a diagnostic report with actionable remediation steps.

What does plugin structural validation check for in a manifest?▼

Structural validation checks that required manifest fields exist, the directory layout is correct, and SKILL.md frontmatter is valid, ensuring the plugin meets conformance standards before release.

When should I run a plugin readiness diagnostic?▼

You should run a plugin readiness diagnostic during readiness reviews, after making edits, or before packaging to ensure manifest compliance, skill quality, and dependency integrity are maintained.

Can I check dependency integrity across inter-skill references and MCPs?▼

Yes, dependency integrity checks verify consistency across MCPs and inter-skill references within the plugin, returning remediation steps if dependencies are missing or inconsistent.

What is the best way to fix plugin manifest conformance errors?▼

The best way to fix manifest conformance errors is to run the validator to generate a prioritized diagnostic report, then follow the actionable remediation steps for each identified issue.

Why does my SKILL.md frontmatter validation fail after editing?▼

SKILL.md frontmatter validation fails when required fields are missing, dependencies become inconsistent across inter-skill references, or the manifest structure no longer conforms after edits.