create-plugin

Create a new Claude Code plugin with proper directory structure and manifest. Use when the user wants to create a new plugin from scratch. Sets up plugin.json, directory structure, and optional components.

Quality

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with excellent workflow clarity and concrete examples. The main weakness is its length - it tries to be both a quick-start guide and a complete reference in one file, leading to some verbosity. The content would benefit from splitting reference tables and detailed examples into separate files while keeping the core creation workflow lean.

Suggestions

Move the detailed manifest field tables and validation error reference to a separate REFERENCE.md file, keeping only essential fields inline

Consolidate the multiple correct/wrong JSON examples into a single clear example per configuration type to reduce redundancy

Remove generic best practices that Claude already knows (e.g., 'use semantic versioning', 'document your plugin') to save tokens

Dimension	Reasoning	Score
Conciseness	The content is comprehensive but includes some redundancy (multiple similar examples for correct/wrong formats) and could be tightened. The tables and structure add value but some sections like 'Best Practices' contain generic advice Claude already knows.	2 / 3
Actionability	Provides fully executable bash commands, complete JSON examples, and copy-paste ready code snippets. The creation process has concrete steps with actual commands, and the migration guide includes a working script.	3 / 3
Workflow Clarity	Clear 7-step creation process with explicit validation step (validate-all-plugins.sh) and testing instructions. The workflow includes important checkpoints like 'IMPORTANT: Register in marketplace.json' and validation before committing.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document (~250 lines) that could benefit from splitting detailed reference material (manifest fields, validation errors) into separate files. No external file references are provided.	2 / 3
	Total	10 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that clearly defines its purpose and when to use it. It excels at specificity and completeness with explicit 'Use when' guidance. The main weakness is limited trigger term coverage - it could benefit from additional natural language variations users might employ when requesting plugin creation.

Suggestions

Add trigger term variations like 'extension', 'scaffold', 'bootstrap plugin', or 'initialize plugin' to capture more user phrasings

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Create a new Claude Code plugin', 'proper directory structure', 'manifest', 'Sets up plugin.json, directory structure, and optional components'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('Create a new Claude Code plugin with proper directory structure and manifest') and when ('Use when the user wants to create a new plugin from scratch') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some natural keywords like 'plugin', 'create', 'new plugin from scratch', but missing common variations users might say such as 'extension', 'add-on', 'scaffold', 'bootstrap', or 'initialize'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche targeting 'Claude Code plugin' creation with distinct triggers like 'plugin.json' and 'plugin from scratch'. Unlikely to conflict with general coding or other plugin-related skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 5 months ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.