CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

62%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./codex/command-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

This skill is well-structured with a clear multi-step workflow and good progressive disclosure intentions, but suffers from significant verbosity and over-explanation of concepts Claude already understands. The conversational 'ask the user' pattern inflates token count without adding actionable value, and the actual command generation—the core purpose—is largely deferred to bundled references that aren't provided. The skill would benefit greatly from trimming explanatory content and including at least one complete, executable command example inline.

Suggestions

Cut 'About Slash Commands', 'When to Use This Skill', and the Summary section entirely—these explain things Claude already knows or repeat content verbatim.

Replace the verbose 'Gather Command Information' interview script with a concise checklist or decision table (name, args, pattern, steps, constraints).

Include at least one complete, copy-paste-ready command example inline rather than deferring all examples to references that may not be available.

Add an explicit validation step after file creation (e.g., verify frontmatter parses correctly, confirm file exists at expected path) to strengthen the workflow.

DimensionReasoningScore

Conciseness

The skill is excessively verbose, explaining concepts Claude already knows (what slash commands are, what markdown files are, what kebab-case is). Sections like 'About Slash Commands', 'When to Use This Skill', and much of the gathering workflow are padded with unnecessary context. The 'Summary' section repeats the workflow verbatim. Many instructions describe conversational patterns ('Ask the user...') that inflate token count significantly.

1 / 3

Actionability

The skill provides some concrete guidance (file paths, mkdir command, frontmatter structure example) but is largely procedural/conversational rather than executable. The 'gather information' steps are interview scripts rather than actionable instructions. The actual command generation step defers to bundled references rather than providing concrete templates or executable examples inline.

2 / 3

Workflow Clarity

The 6-step workflow is clearly sequenced and logically ordered, but lacks validation checkpoints. There's no verification that the generated command file is valid markdown, has correct frontmatter, or that the directory was successfully created. Step 6 (test and iterate) is marked optional rather than being an explicit validation gate.

2 / 3

Progressive Disclosure

References to patterns.md, examples.md, and best-practices.md are well-signaled and one level deep, which is good. However, no bundle files were provided, making it impossible to verify these references exist. Additionally, significant content that could be in the main file (like the command structure template) is kept inline while key actionable content (templates, examples) is deferred to references, creating an imbalance.

2 / 3

Total

7

/

12

Passed

Description

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 description with excellent trigger terms and completeness, clearly specifying both when to use the skill and what it does. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., generating markdown files, defining argument structures). The description also uses passive/imperative voice rather than third person, though this is a minor issue.

Suggestions

Add more specific concrete actions, e.g., 'Generates markdown command files with proper frontmatter, argument definitions, and agent-optimized instructions' to improve specificity.

DimensionReasoningScore

Specificity

The description mentions 'creating a Claude Code slash command' and references 'proper structure and best practices' but doesn't list specific concrete actions like 'generate markdown files', 'define argument schemas', or 'write command templates'. The actions remain somewhat abstract.

2 / 3

Completeness

Clearly answers both 'what' (creating optimized, agent-executable slash commands with proper structure and best practices) and 'when' (explicit 'Use when' clause with multiple trigger phrases like 'create a command', 'make a slash command', 'add a command').

3 / 3

Trigger Term Quality

Includes strong natural trigger terms: 'create a command', 'make a slash command', 'add a command', 'reusable command', 'slash command'. These are phrases users would naturally say when requesting this functionality.

3 / 3

Distinctiveness Conflict Risk

The description targets a very specific niche — Claude Code slash commands — with distinct trigger terms like 'slash command' and 'reusable command' that are unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
jdrhyne/agent-skills
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.