plugin-structure
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
Install with Tessl CLI
npx tessl i github:anthropics/claude-plugins-official --skill plugin-structureOverall
score
77%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 excels at trigger term coverage and distinctiveness, providing many natural phrases users would say when needing plugin help. However, it's structured backwards - it's essentially a list of 'Use when...' triggers without first explaining what the skill actually does. The description needs a clear capability statement before the trigger conditions.
Suggestions
Add a capability statement at the beginning describing what the skill does, e.g., 'Scaffolds Claude Code plugins, generates plugin.json manifests, and organizes component directories.'
Restructure to follow the pattern: '[What it does]. Use when [triggers]' rather than leading with triggers only.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (plugin creation/scaffolding) and mentions several components (commands/agents/skills/hooks, plugin.json, directory layout), but doesn't describe concrete actions Claude will perform - it focuses on trigger scenarios rather than capabilities. | 2 / 3 |
Completeness | The description is essentially all 'when' triggers but lacks a clear 'what does this do' statement. It tells Claude when to use the skill but doesn't explain what actions or outputs the skill provides. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'create a plugin', 'scaffold a plugin', 'understand plugin structure', 'set up plugin.json', 'add commands/agents/skills/hooks'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on Claude Code plugin architecture with unique terms like '${CLAUDE_PLUGIN_ROOT}', 'plugin.json', 'auto-discovery', and 'Claude Code plugin architecture' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive reference document for Claude Code plugin structure with excellent actionability through concrete examples and good organization. However, it's somewhat verbose with redundant explanations and lacks a clear step-by-step workflow for actually creating a plugin, instead reading more like reference documentation than an actionable skill.
Suggestions
Add a 'Quick Start' section at the top with a numbered workflow: 1. Create directory, 2. Add plugin.json, 3. Add first component, 4. Enable plugin, 5. Verify loading
Remove redundant explanations like 'Why it matters' sections and inline usage notes that repeat information Claude already knows
Add explicit validation steps (e.g., 'Verify plugin loaded: check Claude Code settings' or 'Test command: type /command-name')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is comprehensive but includes some redundancy and explanations Claude likely knows (e.g., explaining what kebab-case is, basic JSON structure). The document could be tightened by removing repetitive usage notes and consolidating similar sections. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready examples throughout including complete directory structures, JSON configurations, and file formats. Every component type has executable examples with proper syntax. | 3 / 3 |
Workflow Clarity | While the document explains what each component does, it lacks explicit step-by-step workflows for creating a plugin from scratch. The troubleshooting section helps but there are no validation checkpoints or feedback loops for the plugin creation process itself. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, logical progression from overview to specifics, and appropriate references to external files (references/, examples/) for advanced patterns. Content is appropriately structured with headers and subsections. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
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.