command-creator
This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.
Install with Tessl CLI
npx tessl i github:softaworks/agent-toolkit --skill command-creatorOverall
score
88%
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
90%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 well-structured description with excellent trigger terms and clear 'when to use' guidance. The main weakness is that it doesn't enumerate the specific actions the skill performs (e.g., defining syntax, setting up parameters, creating documentation). The description effectively distinguishes itself from other skills through its specific focus on Claude Code slash commands.
Suggestions
Add specific concrete actions the skill performs, such as 'define command syntax, configure parameters, set up argument handling, create usage documentation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (slash commands) and mentions 'proper structure and best practices' but doesn't list specific concrete actions like 'define command syntax', 'set parameters', or 'configure triggers'. | 2 / 3 |
Completeness | Clearly answers both what ('creating optimized, agent-executable slash commands with proper structure and best practices') and when ('Use when users ask to create a command, make a slash command, add a command, or want to document a workflow'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'create a command', 'make a slash command', 'add a command', 'reusable command' - these are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - 'Claude Code slash command' is distinct and unlikely to conflict with other skills. The trigger terms are specific to this exact use case. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent workflow clarity and progressive disclosure. The actionability is strong with concrete commands and clear decision trees. The main weakness is some unnecessary explanatory content that could be trimmed, particularly the 'About Slash Commands' and 'When to Use This Skill' sections which explain concepts Claude likely already understands.
Suggestions
Remove or significantly condense the 'About Slash Commands' section - Claude understands what slash commands are
Consider removing the 'When to Use This Skill' section as this context is typically provided by the skill's metadata/description, not the body content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., 'About Slash Commands' section explains what Claude likely already knows) and could be tightened. However, it's not excessively verbose and most content serves a purpose. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific bash commands, exact file paths, clear step-by-step workflows, and explicit examples of correct vs incorrect naming conventions. The workflow steps are copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (Steps 1-6), explicit decision points (auto-detect location logic), and iteration loops (Step 6). Each step has clear actions and the workflow handles both project and global contexts. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview in main file and one-level-deep references to patterns.md, examples.md, and best-practices.md. References are clearly signaled with bold labels and explicit guidance on when to load each. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%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 |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 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.