tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill plugin-creatorCreate 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'.
Validation
75%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
Implementation
22%This skill is essentially a skeleton template with no actual content. It references creating plugins with 'proper structure, validation, and marketplace integration' in the description but provides zero concrete guidance on how to accomplish any of these tasks. The Instructions section is literally empty, making this skill non-functional.
Suggestions
Replace the '[Step-by-step for Claude]' placeholder with actual numbered steps for plugin creation, including specific commands and file operations
Add executable code examples showing the plugin structure, required files, and validation commands
Include concrete examples of plugin manifest/configuration with actual field names and values
Resolve the '{baseDir}' placeholder to actual paths or explain how to determine the base directory
| 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. '[Step-by-step for Claude]' is a placeholder, not instructions. There's no executable code, no specific commands, and no actual steps for creating plugins. | 1 / 3 |
Workflow Clarity | There is no workflow defined. The Instructions section is empty except for a placeholder comment. For a plugin creation task that likely involves multiple steps (scaffolding, validation, marketplace integration), this is completely inadequate. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is so sparse that the references feel like deflection rather than appropriate content splitting. The '{baseDir}' placeholder suggests incomplete templating. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
82%This description has strong completeness with explicit 'Use when' guidance and good trigger term coverage. However, the generic triggers ('generate', 'create') pose conflict risk with other skills, and the capabilities could be more specific about what 'proper structure' and 'validation' actually entail.
Suggestions
Make triggers more specific to reduce conflict risk - e.g., 'create plugin', 'new plugin', 'scaffold plugin' rather than generic 'create' or 'generate'
Add more specific capability details - e.g., 'generates manifest.json, validates schema, registers with marketplace API' instead of vague 'proper structure, validation'
| 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 | Good coverage of 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 | The specific mention of 'AI assistant-code-plugins repository' provides some distinctiveness, but generic triggers like 'generate' and 'create' could easily conflict with other creation-focused skills. | 2 / 3 |
Total | 10 / 12 Passed |
Reviewed
Table of Contents
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.