plugin-reviewer

Validate Claude Code plugin manifests, component registration, and portability.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill plugin-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-reviewer
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/kronen/skills/plugin-reviewer
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill plugin-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the rigorous review of Claude Code plugins, ensuring they meet manifest correctness, component registration, portability, and settings pattern standards, preventing errors and improving ecosystem health.

Core Features & Use Cases

  • Manifest Validation: Checks plugin.json and ecosystem.json for required fields, correct formats, and forbidden entries.
  • Component Auditing: Verifies that all files on disk correspond to entries in ecosystem.json and vice-versa.
  • Portability Checks: Identifies hardcoded paths and ensures cross-platform compatibility.
  • Use Case: Before merging a new plugin into the main repository, use this Skill to perform an automated audit that catches common errors related to manifest structure, component registration, and portability issues.

Quick Start

Run the plugin-reviewer skill to audit the 'my-new-plugin' directory.

Frequently Asked Questions about plugin-reviewer

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

FAQPage Schema
How do I validate plugin.json and ecosystem.json files before merging?

To validate plugin manifests, run an automated audit that checks plugin.json and ecosystem.json for required fields, correct formats, and forbidden entries to prevent structural errors before merging.

What is a plugin portability check and when do I need it?

A plugin portability check identifies hardcoded paths in your codebase to ensure cross-platform compatibility. You need it when auditing plugins for ecosystem health and verifying that components function correctly across different operating environments.

How do I audit files on disk against ecosystem.json component registration?

To audit component registration, run a validation process that verifies all files on disk correspond exactly to entries in ecosystem.json and vice-versa, catching missing or orphaned components during an ecosystem audit.

Can I use an automated review to check marketplace registration correctness?

Yes, you can use an automated review to verify marketplace registration by checking manifest correctness and component registration quality, ensuring plugins meet required settings patterns and spec compliance before publication.

What are common limitations when reviewing hardcoded paths for portability issues?

When checking hardcoded paths for portability issues, limitations arise if the plugin relies on platform-specific environment variables or undocumented settings patterns, making cross-platform compatibility difficult to verify automatically without strict spec compliance.

What's the best way to audit existing plugins for manifest correctness and settings patterns?

The best way to audit existing plugins is running an automated review that checks manifest correctness, component registration, and settings patterns, ensuring files on disk match ecosystem.json and meet quality review stage standards.