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

88%

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

Quality

Content

77%

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

The body is highly actionable with executable examples and well-sequenced validation workflows, but it is verbose for its budget and carries a broken reference to a non-existent `examples/` directory alongside an over-inline plugin section that would benefit from extraction into a reference file.

Suggestions

Remove or fix the dangling `examples/` directory reference at the end of the body, since that directory is not present in the bundle.

Trim obvious benefit lists and consolidate the repeated review-code examples that appear verbatim across the File Format, Common Patterns, and Validation sections to reduce token bloat.

Move the lengthy Plugin-Specific Features and Integration sections into a dedicated reference file (or expand plugin-features-reference.md) and link to it from the body, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	At roughly 830 lines the body includes padding such as obvious benefit lists ("Reusability", "Consistency", "Sharing", "Efficiency") and repeated verbatim review-code examples across multiple sections, though it avoids explaining basic Markdown/YAML concepts and retains genuinely useful reference material.	2 / 3
Actionability	Packed with concrete, copy-paste-ready examples using `!`backtick`` bash execution, `@${CLAUDE_PLUGIN_ROOT}/...` references, and full `$ARGUMENTS`/`$1`/`$2` expansions shown with input-to-output mappings, matching the fully executable anchor.	3 / 3
Workflow Clarity	Provides explicit validation checkpoints (e.g., `!`echo "$1" \| grep -E...``, `!`test -f $1...``), if/otherwise error-recovery branches, and sequenced multi-step workflows (Workflow Pattern, Phase 1-4 Multi-Component), matching the anchor for clear sequences with explicit validation.	3 / 3
Progressive Disclosure	Offloads detail to clearly signaled one-level-deep references (plugin-features-reference.md, frontmatter-reference.md) that exist in the bundle, but the final line points to an `examples/` directory that does not exist, and the large inline Plugin-Specific Features section could itself live in a reference file.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 explicit, action-oriented, and written in third person, with a strong "Use when..." trigger clause and concrete trigger terms that a user would naturally say. It clearly establishes a distinct niche around slash command development with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as "create a slash command", "define command arguments", "use command frontmatter", and "organize commands", matching the anchor for multiple specific concrete actions rather than vague language.	3 / 3
Completeness	The explicit "This skill should be used when..." clause answers when with concrete triggers, while the named actions convey what the skill does, satisfying both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Includes natural phrasings users would actually say ("create a slash command", "add a command", "write a custom command", "organize commands", "interactive command") plus broad "command development best practices", giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to Claude Code slash command development with distinct triggers, making it clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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: 2f7766f

Reviewed: about 15 hours 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.