validate-plugin

Validate plugin directories against claude-play marketplace quality standards.

Updated Oct 15, 2025
One-click install
npx skills add https://github.com/odeciojunior/claude-play --skill validate-plugin-odeciojunior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-plugin
Source: https://github.com/odeciojunior/claude-play/tree/main/plugins/marketplace-tools/skills/validate-plugin
Command: npx skills add https://github.com/odeciojunior/claude-play --skill validate-plugin-odeciojunior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates quality validation of claude-play plugin directories to catch structural issues, missing metadata, insecure patterns, and registration problems before publishing.

Core Features & Use Cases

  • Directory and metadata validation: Verifies that plugin directory name matches .claude-plugin/plugin.json and required fields exist.
  • SKILL.md and content checks: Ensures each SKILL.md has proper YAML frontmatter and supported attributes, and reports unsupported or missing fields.
  • Security and hygiene scans: Greps for hardcoded absolute paths and sensitive data patterns, and checks marketplace registration status.
  • Use Case: Use this Skill when reviewing a new plugin submission or running pre-commit checks to produce an OK/WARN/FAIL summary across seven standardized checks.

Quick Start

Run the validate-plugin skill against the target plugin directory to produce a standardized validation report.

Frequently Asked Questions about validate-plugin

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

FAQPage Schema
How do I validate a plugin directory for marketplace compliance before submission?

To validate a plugin directory for marketplace compliance, run checks against the target path to detect missing metadata, invalid SKILL.md frontmatter, hardcoded paths, and sensitive data patterns. This produces a standardized OK, WARN, and FAIL summary across seven defined checks for pre-commit reviews and submissions.

What does a plugin marketplace quality check look for in SKILL.md frontmatter?

A plugin marketplace quality check parses SKILL.md files to ensure proper YAML frontmatter exists and contains supported attributes. It reports any unsupported or missing fields to prevent structural issues before publishing.

How do I scan a plugin for hardcoded paths and sensitive data patterns before publishing?

To scan a plugin for hardcoded paths and sensitive data patterns, run security and hygiene checks that glob across plugin files. This detects insecure absolute paths and sensitive data to resolve vulnerabilities prior to marketplace registration.

Does plugin validation require any external dependencies to run pre-commit checks?

Plugin validation requires no external dependencies to run pre-commit checks. It operates standalone by parsing plugin.json and SKILL.md frontmatter, globbing skills, and running pattern checks to produce OK, WARN, and FAIL outcomes.

Why does my plugin fail marketplace registration validation despite having a plugin.json file?

Plugin marketplace registration validation fails if the directory name does not match the .claude-plugin/plugin.json identifier, if required fields are missing, or if the plugin is not properly registered in the marketplace database.