CtrlK
BlogDocsLog inGet started
Tessl Logo

commands-create-slash-command

Create or update Agent Zero slash commands for the built-in Commands plugin. Use when the user asks to add, edit, duplicate, or refine a reusable /command backed by YAML config plus text/python content files.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 body is concise and mostly actionable with concrete paths, config keys, and placeholder syntax, but it ships broken references to template files that are absent and lacks a validation step in its file-writing workflow.

Suggestions

Add a validation/verification step to the Editing Workflow (e.g., after saving, confirm the command is discoverable or test the /name invocation) so destructive file writes have a checkpoint.

Either provide the referenced template.command.yaml and template.command.txt bundle files under references/ or scripts/, or remove the reference to them and inline a minimal example config and text template.

Include one small complete YAML config example inline so the authoring guidance is fully copy-paste ready without depending on external templates.

DimensionReasoningScore

Conciseness

Lean and tightly structured with no padding or explanation of concepts Claude already knows; every section (Source Of Truth, Scope Resolution, File Rules, Output Contract) earns its place.

5 / 5

Actionability

Provides concrete file names, required/optional config keys, exact scope paths, the run(payload) hook, and placeholder syntax ({raw}, {args.positional.0}). A literal full YAML/text template example inline would make it fully copy-paste ready rather than relying on referenced template files.

4 / 5

Workflow Clarity

The Editing Workflow is a clear 6-step sequence, but it writes/overwrites config and content files without any validation or verification checkpoint (e.g., confirming the command loads or that the invocation works), so per the destructive-operation cap it cannot exceed 3.

3 / 5

Progressive Disclosure

The body references bundled templates (template.command.yaml, template.command.txt) that do not exist in any references/scripts/assets directory, so the signaled navigation points to missing material and the disclosure is not actually resolvable.

3 / 5

Total

15

/

20

Passed

Description

92%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 strong description that concisely states concrete capabilities and gives explicit, natural-sounding trigger guidance tied to a well-scoped plugin niche. The only minor gap is the absence of file-extension synonyms in the trigger terms.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("Create or update", "add, edit, duplicate, or refine") and the backing artifacts ("YAML config plus text/python content files"), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ("Create or update Agent Zero slash commands... backed by YAML config plus text/python content files") and when ("Use when the user asks to add, edit, duplicate, or refine a reusable /command").

5 / 5

Trigger Term Quality

Strong natural phrasings users would say ("add, edit, duplicate, or refine a reusable /command", "slash commands", "commands plugin"), but no file-extension or synonym variants like ".yaml" or ".command.yaml" that users might mention.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche ("Agent Zero slash commands for the built-in Commands plugin") with distinct triggers, making it unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
agent0ai/agent-zero
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.