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'.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill plugin-creator

What are skills?

Quality

52%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/examples/jeremy-plugin-tool/skills/plugin-creator/SKILL.md

SKILL.md

Review

Evals

Discovery

82%

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 description has strong completeness with explicit 'Use when' guidance and good trigger terms that users would naturally say. However, the generic triggers ('generate', 'create', 'scaffold') without more specific qualifiers create potential conflict with other creation-focused skills. The specificity of capabilities could be improved by detailing what 'proper structure' and 'validation' actually entail.

Suggestions

Narrow the generic triggers by qualifying them more specifically, e.g., 'Use when generating plugins, creating plugin templates, or scaffolding plugin projects' to reduce conflict with other creation skills.

Add more specific capability details such as what validation rules are applied or what marketplace integration involves (e.g., 'generates manifest files, validates plugin schema, configures marketplace metadata').

Dimension	Reasoning	Score
Specificity	Names the domain (AI assistant code plugins) and some actions (proper structure, validation, marketplace integration), but lacks comprehensive detail about what specific structures or validations are created.	2 / 3
Completeness	Clearly answers both what (creates new AI assistant code plugins with structure, validation, marketplace integration) and when (explicit 'Use when' clause with trigger phrases like 'generate', 'create', 'scaffold').	3 / 3
Trigger Term Quality	Includes good natural trigger terms: 'creating a plugin', 'new plugin', 'plugin from template', 'generate', 'create', 'scaffold' - these are terms users would naturally say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	While 'AI assistant-code-plugins repository' is specific, the generic triggers 'generate', 'create', 'scaffold' could easily conflict with other creation/scaffolding skills. The scope is somewhat narrowed by 'plugin' mentions but still has overlap risk.	2 / 3
	Total	10 / 12 Passed

Implementation

22%

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

This skill is essentially a skeleton template with no actual content. It claims to automate plugin creation with validation and marketplace integration but provides no instructions, no code examples, no workflow steps, and no concrete guidance. The description promises specific functionality that the body completely fails to deliver.

Suggestions

Add actual step-by-step instructions in the Instructions section showing how to create a plugin (e.g., directory structure, required files, validation commands)

Include executable code examples for plugin scaffolding, such as a script or command sequence to generate the plugin structure

Define a clear workflow with validation checkpoints: create structure -> validate manifest -> test locally -> prepare for marketplace

Replace generic prerequisites with specific requirements (e.g., 'Node.js 18+', 'plugin-cli installed via npm install -g @assistant/plugin-cli')

Dimension	Reasoning	Score
Conciseness	The content is brief but mostly because it lacks substance rather than being efficiently dense. Generic placeholders like 'appropriate file access permissions' and 'required dependencies installed' add no value.	2 / 3
Actionability	The skill provides no concrete guidance whatsoever. The Instructions section is literally empty with just '[Step-by-step for Claude]' placeholder text. No code, no commands, no specific steps for creating plugins.	1 / 3
Workflow Clarity	There is no workflow defined. The skill describes creating plugins with 'proper structure, validation, and marketplace integration' but provides zero steps, no validation checkpoints, and no sequence of operations.	1 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main content is so empty that the references feel like deflection rather than appropriate content splitting. The '{baseDir}' placeholder suggests incomplete templating.	2 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

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.