commands-create-slash-command

Create or edit reusable Agent Zero /commands with YAML and text/Python templates.

Quality

80%

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 ./plugins/_commands/skills/commands-create-slash-command/SKILL.md

Quality

Content

82%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.

A tight, highly actionable body with correct file conventions, scope resolution, and a clear editing workflow. The main weaknesses are the dangling reference to template files absent from the bundle and the lack of any validation/verification step after saving.

Suggestions

Fix the template reference: either bundle template.command.yaml / template.command.txt (or inline a minimal worked example of both) so the pointer in File Rules resolves.

Add a post-save verification step to the Editing Workflow, e.g. re-read the saved YAML to confirm it parses and that required keys (name, description, type) are present.

Include one complete example config (a short <slug>.command.yaml with name/description/type/argument_hint) so the 'Source Of Truth' key list becomes copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense with project-specific facts — file naming rules, required/optional config keys, exact scope folder paths, and an output contract — with no padding and no explanation of concepts Claude already knows. Every token earns its place, matching the 'lean and efficient' anchor; it is not a 4 because there is no over-explanation to trim.	5 / 5
Actionability	Guidance is mostly executable: exact file patterns ('<slug>.command.yaml', '<slug>.txt', '<slug>.py'), required keys ('name', 'description', 'type'), concrete scope paths, placeholder syntax ('{raw}', '{args.positional.0}'), and a report format. It falls short of 5 because it references 'bundled templates in template.command.yaml and template.command.txt' that are not present in the skill's bundle, and no inline example of a complete config or template is given.	4 / 5
Workflow Clarity	The Editing Workflow is a clear 6-step sequence with a meaningful checkpoint (check for an existing command, load it first, preserve unknown frontmatter keys) and an explicit reporting step. It is not a 5 because there is no post-save validation step (e.g. re-reading the saved YAML to confirm it parses) or error-recovery feedback loop, though the operation is not destructive or batch-heavy enough to trigger the cap at 3.	4 / 5
Progressive Disclosure	The ~60-line body is well organized into short, labeled sections with everything appropriately inline for a skill of this size, and only a single one-level reference outward. It is not a 5 because that outward reference ('the bundled templates in template.command.yaml and template.command.txt') points to files that do not exist in the bundle, leaving navigation to the detailed material broken.	4 / 5
	Total	17 / 20 Passed

Description

70%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.

A concise, concrete description with a clear niche and good natural keywords, weakened mainly by the absence of an explicit 'Use when...' clause in the description field itself. Trigger coverage omits the common phrase 'slash command'.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user asks to create, add, or edit a slash command for Agent Zero's commands plugin.'

Include the natural phrase 'slash command' (and synonyms like 'add a command') directly in the description text rather than only '/commands'.

Briefly name one or two more capabilities (e.g. choosing project vs. global scope) to close the minor coverage gap toward a comprehensive action list.

Dimension	Reasoning	Score
Specificity	The description names its domain ('reusable Agent Zero /commands') and concrete artifacts ('YAML and text/Python templates') alongside two actions ('Create or edit'), which goes beyond the anchor-3 example's bare two actions, but coverage has minor gaps (no mention of scoping, config keys, or the plugin workflow), so it fits 'several specific actions; minor gaps' rather than a comprehensive 5.	4 / 5
Completeness	The 'what' is clear ('Create or edit reusable Agent Zero /commands with YAML and text/Python templates') but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description — the when-intent lives only in the separate frontmatter triggers list — which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent from the description field, not merely weak.	3 / 5
Trigger Term Quality	Natural terms like 'create', 'edit', 'commands', 'templates', 'YAML', and 'Python' are present and match what a user would say, but the very common phrase 'slash command' (and variations like 'add') is missing from the description itself — it only appears as '/commands' — so coverage is good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	'Agent Zero /commands' carves out a clear niche with distinct triggers (the _commands plugin, command YAML + template files); there is minimal realistic overlap with generic skill descriptions, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: agent0ai/agent-zero
Path: plugins/_commands/skills/commands-create-slash-command/SKILL.md
Commit: e3051fb

Reviewed: 10 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.