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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/examples/jeremy-plugin-tool/skills/plugin-creator/SKILL.md

Quality

Content

70%Weight 40%Scale 1-3

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

The content is a well-structured, validated multi-step workflow with clean progressive disclosure into real reference files, but it carries minor redundancy in the Examples section and delegates the actual file templates to references rather than providing copy-paste-ready content inline.

Suggestions

Trim the Examples section so it shows only the trigger phrasing and points to the Instructions for the process, removing the restated 'plugin.json, README, LICENSE, sync, validate' steps.

Inline the minimal plugin.json skeleton (or a pointer with the exact template snippet) so the body is executable without opening file-templates.md for the most common case.

Dimension	Reasoning	Score
Conciseness	The body is lean, uses lists/tables, and avoids explaining concepts Claude already knows, but the Examples section restates the Instructions steps (plugin.json, README, LICENSE, add to marketplace, sync, validate) creating redundant tokens.	2 / 3
Actionability	It provides concrete commands (pnpm run sync-marketplace, ./scripts/validate-all-plugins.sh, jq empty), a directory tree, and required frontmatter fields, but the actual generated-file templates live in file-templates.md rather than being copy-paste ready inline, leaving the body incomplete on its own.	2 / 3
Workflow Clarity	Nine steps are clearly sequenced with an explicit validation checkpoint and fix loop ('Validate the new plugin by running ./scripts/validate-all-plugins.sh ... Fix any reported issues before completion'), reinforced by an error-cause-solution table.	3 / 3
Progressive Disclosure	The body is an overview that signals four real, one-level-deep references (plugin-creation-process.md, file-templates.md, examples.md, errors.md) in a Resources section, with detail appropriately split out and easy to navigate.	3 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 covers both capability and trigger guidance and is narrowly scoped to a plugin-creation workflow, but it leans on generic trigger verbs ('generate', 'create', 'new content') that raise conflict risk and describe actions at a high level of abstraction.

Suggestions

Replace the generic 'Use when generating or creating new content' with plugin-specific triggers, e.g. 'Use when the user asks to create, scaffold, or generate a new Claude Code plugin or plugin template.'

Tighten specificity by naming concrete outputs ('scaffold directory structure, generate plugin.json, sync marketplace.json, and validate with validate-all-plugins.sh') instead of 'proper structure, validation, and marketplace integration'.

Drop standalone 'generate'/'create' trigger terms that conflict with other creation skills in favor of compound phrases tied to 'plugin'.

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ('creates new AI assistant code plugins with proper structure, validation, and marketplace integration') but the actions are abstract ('proper structure') rather than the granular concrete verbs seen in the score-3 anchor.	2 / 3
Completeness	Explicitly answers both what it does (creates plugins with structure, validation, marketplace integration) and when to use it via a present 'Use when generating or creating new content' clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Includes natural, domain-relevant terms ('scaffold', 'creating a plugin', 'plugin from template') but pairs them with overly generic triggers ('generate', 'create', 'creating new content') that lack specificity and miss tighter variations.	2 / 3
Distinctiveness Conflict Risk	It carves a niche ('specific to AI assistant-code-plugins repository workflow') but the generic 'Use when generating or creating new content' and 'Trigger with phrases like generate, create' would overlap with many creation skills, matching the score-2 anchor.	2 / 3
	Total	9 / 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
Path: plugins/examples/jeremy-plugin-tool/skills/plugin-creator/SKILL.md
Commit: c4eafaf

Reviewed: 1 day 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.