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.

76

Quality

96%

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

92%

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

The body is a tight, actionable, well-sequenced guide with concrete file formats, config keys, and an editing workflow. Its one real weakness is progressive disclosure: it references bundled templates that are not actually present in the skill bundle.

Suggestions

Add the referenced template files (template.command.yaml and template.command.txt) to a references/ or assets/ directory, or remove the 'Use the bundled templates' instruction if no bundle ships with the skill.

Optionally add a brief verification step to the Editing Workflow (e.g., re-read the saved YAML to confirm it parses and keys are preserved) to strengthen the checkpoint beyond the existence check.

Make the scope folder examples consistent with the Output Contract paths (the Source Of Truth uses relative 'usr/plugins/...' while the Output Contract uses '/a0/usr/plugins/...') to avoid ambiguity.

DimensionReasoningScore

Conciseness

The body is lean and operational with no concept explanations Claude already knows; every line earns its place (file formats, paths, config keys, tokens), matching the 'lean and efficient' anchor rather than the 'mostly efficient but could be tightened' level 2.

3 / 3

Actionability

Provides concrete, executable guidance: exact file naming (`<slug>.command.yaml`, `<slug>.py`), required config keys, `run(payload)`, and placeholder tokens (`{raw}`, `{args.positional.0}`), which is copy-paste ready rather than vague or pseudocode.

3 / 3

Workflow Clarity

The Editing Workflow is a clear 6-step sequence with an explicit existence-check checkpoint ('Check whether a command file already exists' / 'load the file first and preserve unknown frontmatter keys'); as a simple single-purpose skill with non-destructive writes, it meets the bar for level 3 rather than capping at 2 for missing validation on risky operations.

3 / 3

Progressive Disclosure

The body is well-organized into short sections (which would otherwise score 3 for a simple skill), but it instructs Claude to 'Use the bundled templates in template.command.yaml and template.command.txt' and no such bundle files exist in references/scripts/assets, so a referenced path is not actually present — a structure defect that drops it below level 3.

2 / 3

Total

11

/

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 concise, uses correct third-person voice, and cleanly specifies both the concrete capabilities and an explicit 'Use when' trigger. It is distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Create or update', 'add, edit, duplicate, or refine') and the concrete mechanism ('YAML config plus text/python content files'), matching the 'lists multiple specific concrete actions' anchor rather than the partial domain-only level 2.

3 / 3

Completeness

Explicitly answers both 'what' (create/update slash commands backed by YAML+content files) and 'when' via the explicit 'Use when the user asks to add, edit, duplicate, or refine...' clause, so it does not cap at level 2.

3 / 3

Trigger Term Quality

Covers natural user phrasings ('add, edit, duplicate, or refine a reusable /command') that a user would actually say, giving good coverage of common variations rather than just some relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'Agent Zero slash commands for the built-in Commands plugin' with a distinctive backing format, giving a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.