Commands Create Slash Command
Agent Buildingcommands-create-slash-commandCommands Create Slash Command is an Agent Skill for agent building published in the agent0ai/agent-zero repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/agent0ai/agent-zero/blob/HEAD/plugins/_commands/skills/commands-create-slash-command/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/commands-create-slash-command, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Commands Plugin Slash Command Authoring
Use this skill when the user wants a reusable /command for Agent Zero's built-in _commands plugin.
Source Of Truth
- Slash commands are file-backed, not database rows.
- Each command uses:
- one config file:
<slug>.command.yaml - one content file:
- text template:
<slug>.txt, or - python hook:
<slug>.py
- text template:
- one config file:
- Required config keys:
namedescriptiontype(textorscript)
- Optional config keys:
argument_hintinclude_history(script commands)
- Preserve unknown config keys when editing existing commands.
Scope Resolution
Choose the target folder from the requested scope:
- Project:
usr/projects/<project>/.a0proj/plugins/_commands/commands/ - Global fallback:
usr/plugins/_commands/commands/
If the user does not specify a scope, prefer the active chat scope when it is clear. Otherwise use the global scope.
File Rules
- Config file format:
<slug>.command.yaml - Slash command name should be lowercase and hyphenated, for example
explain-code - For text commands, keep the
.txttemplate concise and directly reusable - For script commands, implement
run(payload)in the.pyfile - If the command expects trailing input, use
{raw},{args.positional.0}, or{args.flags.some_flag}
Use the bundled templates in template.command.yaml and template.command.txt when creating a new text command from scratch.
Editing Workflow
- Determine scope and final slash command name.
- Check whether a command file already exists in that scope.
- If it exists, load the file first and preserve unknown frontmatter keys.
- Update YAML config and template/script content.
- Save the file in the correct scope folder.
- Report:
- the saved config path
- the saved content path
- the slash command name in
/nameform
Output Contract
After saving, explicitly state the final file path and the exact slash command invocation, for example:
Saved config: /a0/usr/plugins/_commands/commands/explain-code.command.yamlSaved content: /a0/usr/plugins/_commands/commands/explain-code.txtInvoke with: /explain-code