Create a new Claude Code slash command with proper YAML frontmatter structure. Use when the user wants to add a custom slash command to a plugin. Handles command file creation with description, argument hints, allowed tools, and all advanced features.
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/claude-code-dev/skills/create-command/SKILL.mdQuality
Discovery
89%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 is a solid skill description that clearly communicates its purpose and includes explicit 'Use when' guidance. The trigger terms are natural and specific to the domain. The main weakness is the vague 'all advanced features' phrase which doesn't specify what those features are.
Suggestions
Replace 'all advanced features' with specific examples like 'file patterns, model selection, custom prompts' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Claude Code slash commands) and mentions some actions (command file creation, YAML frontmatter structure), but doesn't comprehensively list specific capabilities beyond 'handles...all advanced features' which is vague. | 2 / 3 |
Completeness | Clearly answers both what ('Create a new Claude Code slash command with proper YAML frontmatter structure') and when ('Use when the user wants to add a custom slash command to a plugin') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'slash command', 'custom slash command', 'plugin', 'YAML frontmatter', 'command file', 'argument hints', 'allowed tools'. Good coverage of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Claude Code slash commands with YAML frontmatter. Unlikely to conflict with other skills due to the specific combination of 'slash command', 'plugin', and 'YAML frontmatter' triggers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable guidance for creating slash commands with excellent concrete examples and clear syntax documentation. However, it could be more concise by reducing redundancy between explanation sections and examples, and would benefit from a clearer step-by-step workflow for the actual command creation process rather than just documenting all the features.
Suggestions
Add a 'Quick Start' workflow section at the top with numbered steps: 1. Choose command type (project/personal), 2. Create file at correct location, 3. Add frontmatter, 4. Write instructions, 5. Test with /help and invocation
Split advanced topics (SlashCommand tool integration, complex examples like Deploy Command) into a separate ADVANCED.md or EXAMPLES.md file to reduce main document length
Consolidate the examples section - several examples repeat concepts already covered in the feature explanations above them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the examples section repeats concepts already explained in earlier sections, and some tables could be consolidated. The comparison table at the end adds value but the overall document could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready examples throughout. Every concept is illustrated with concrete markdown code blocks showing exact file formats, frontmatter fields, and usage patterns. | 3 / 3 |
Workflow Clarity | While the document clearly explains command structure and options, it lacks explicit workflow steps for creating a command (e.g., 1. Choose location, 2. Create file, 3. Add frontmatter, 4. Test). The Deploy Command example shows good validation steps but the overall skill doesn't guide through the creation process sequentially. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's a monolithic document that could benefit from splitting advanced topics (SlashCommand tool integration, complex examples) into separate reference files. No external file references are provided for deeper dives. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
0ebe7ae
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.