plugin-creator

Create automatically creates new AI assistant code plugins with proper structure, validation, and marketplace integration when user mentions creating a plugin, new plugin, or plugin from template. specific to AI assistant-code-plugins repository workflow. Use when generating or creating new content. Trigger with phrases like 'generate', 'create', or 'scaffold'.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

The content is well-structured and highly actionable, with a clearly sequenced workflow that includes explicit validation and a feedback loop, plus clean progressive disclosure to verified reference files. The main weakness is mild redundancy in the Examples section and the inline directory tree.

Suggestions

Trim the Examples section, which restates the create→marketplace→sync→validate flow already in Instructions; instead summarize each scenario in one line and defer detail to examples.md.

Move the inline plugin directory tree into file-templates.md to avoid duplicating template content that is already referenced there.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence without explaining basic concepts, but the Examples section reiterates the create→generate→marketplace→sync→validate flow already covered in Instructions, and the inline directory tree duplicates content that lives in file-templates.md, so it could be tightened.	2 / 3
Actionability	Guidance is concrete and executable: exact paths (plugins/[category]/[plugin-name]/), specific commands (pnpm run sync-marketplace, ./scripts/validate-all-plugins.sh), required frontmatter fields, and pointers to real template files — fully actionable for an instruction-only skill.	3 / 3
Workflow Clarity	A clear 9-step sequence includes an explicit validation checkpoint (step 9: run validate-all-plugins.sh) with a fix-before-completion feedback loop and an error-handling table for recovery, matching the anchor for clear sequence with explicit validation.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to four real, one-level-deep reference files (plugin-creation-process.md, file-templates.md, examples.md, errors.md), all verified present, with a dedicated Resources section for easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

77%

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

The description clearly states capabilities and includes explicit trigger guidance, giving it strong completeness and specificity. Its weakness is trigger quality and conflict risk: the generic 'create'/'generate' terms dilute the plugin-specific triggers and invite overlap with unrelated skills.

Suggestions

Replace the over-generic triggers 'generate' and 'creating new content' with plugin-specific phrasing (e.g., 'Use when the user asks to scaffold, create, or generate a Claude Code plugin') to reduce conflict with non-plugin creation skills.

Fix the redundant 'Create automatically creates' opening and the lowercase 'specific to AI assistant-code-plugins repository workflow' fragment so the description reads as clean third-person prose.

Lead with the concrete capability clause and keep triggers narrowly tied to 'plugin' to sharpen distinctiveness from other scaffolding skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'creates new AI assistant code plugins with proper structure, validation, and marketplace integration' — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It explicitly answers both what ('creates new AI assistant code plugins with proper structure, validation, and marketplace integration') and when ('when user mentions creating a plugin... Use when generating or creating new content. Trigger with phrases like generate, create, or scaffold').	3 / 3
Trigger Term Quality	Plugin-specific phrases like 'creating a plugin, new plugin, or plugin from template' and 'scaffold' are natural, but 'generate', 'create', and 'creating new content' are overly generic terms a user would say for almost any skill, so coverage is mixed rather than strong.	2 / 3
Distinctiveness Conflict Risk	The plugin-creation framing gives it a niche, but the generic triggers 'generate', 'create', and 'creating new content' would cause it to overlap with many other creation-oriented skills, so it is only somewhat distinguishable.	2 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 days 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.