command-development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/command-development/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

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

The content excels at actionability with many executable examples and reasonable workflow patterns, but it is held back by verbosity (repeated examples, padded explanations) and weak progressive disclosure (unreferenced bundle files and a dangling examples/ pointer).

Suggestions

Deduplicate repeated examples (the security-review block appears several times) and trim restated basics like the 'Key concepts' list and 'Reusability/Consistency/Sharing/Efficiency' bullets to reduce padding.

Either reference the five unused bundle files (advanced-workflows, documentation-patterns, interactive-commands, marketplace-considerations, testing-strategies) from the relevant body sections or remove them, and remove or create the non-existent 'examples/' directory referenced on the last line.

Move the inlined frontmatter field reference and plugin-specific patterns into their existing reference files, leaving SKILL.md as a concise overview with clearly signaled one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the same security-review example is repeated verbatim multiple times, basic concepts are restated ('Reusability: Define once, use repeatedly', a 'Key concepts' bullet list echoing the title), and frontmatter field explanations are padded. Not a 1 because the material is accurate and useful, but it does not reach the 'mostly efficient' bar of 3.	2 / 5
Actionability	Provides numerous concrete, copy-paste-ready command examples covering $ARGUMENTS, positional args, @file references, bash !`...` execution, validation, and plugin patterns, matching the anchor for fully executable guidance across common cases.	5 / 5
Workflow Clarity	Pattern catalogs (Review, Testing, Workflow) show clear numbered sequences, and the Validation Patterns section includes if/else feedback loops with error handling; falls short of 5 because these are reference patterns rather than one coherently sequenced workflow with explicit checkpoints throughout.	4 / 5
Progressive Disclosure	Seven reference files exist but only two are actually cited in the body (plugin-features-reference.md and frontmatter-reference.md), the body inlines substantial reference-grade material, and it points to a non-existent 'examples/' directory. Structure and signaling are present but with real navigation gaps, so it sits at the 3 anchor rather than the well-organized 4.	3 / 5
	Total	14 / 20 Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong on trigger coverage and distinctiveness, with explicit and abundant 'when' guidance that satisfies the completeness floor. Its main weakness is that the 'what' (the skill's performed capabilities) is implied through trigger phrasing rather than stated as a clean capability sentence.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete capabilities ('create a slash command', 'define command arguments', 'use command frontmatter', 'interactive command', 'use AskUserQuestion in command') with only minor gaps; not a full 5 because the performed actions lean toward trigger scenarios rather than a comprehensive capability list.	4 / 5
Completeness	Explicit, extensive 'when' trigger guidance is present ('This skill should be used when the user asks to...'), and 'what' is implied through the trigger list, but the 'what' is not stated as a crisp capability sentence, keeping it just below the 5 anchor.	4 / 5
Trigger Term Quality	Comprehensive natural-phrase coverage with synonyms ('create a slash command', 'add a command', 'write a custom command', 'interactive command') plus specific technical triggers, matching the anchor for full coverage including variations.	5 / 5
Distinctiveness Conflict Risk	Targets a clear, narrow niche (Claude Code slash command development) with highly specific triggers, making conflict with unrelated skills unlikely.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

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
skill_md_line_count	SKILL.md is long (836 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/command-development/SKILL.md
Commit: 6ed46da

Reviewed: 20 days ago

Table of Contents

Discovery Implementation Validation

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.