How do I install the Commands Create Slash Command skill?

Run npx skillmds@latest add gabrielmoreira/commands-create-slash-command in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commands Create Slash Command safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commands Create Slash Command?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commands Create Slash Command free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commands Create Slash Command?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commands Create Slash Command by gabrielmoreira

Name: Commands Create Slash Command
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

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.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

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
Required config keys:
- name
- description
- type (text or script)
Optional config keys:
- argument_hint
- include_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 .txt template concise and directly reusable
For script commands, implement run(payload) in the .py file
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 /name form

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.yaml
Saved content: /a0/usr/plugins/_commands/commands/explain-code.txt
Invoke with: /explain-code

---name: commands-create-slash-commanddescription: 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.--- # 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` - Required config keys: - `name` - `description` - `type` (`text` or `script`) - Optional config keys: - `argument_hint` - `include_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 `.txt` template concise and directly reusable - For script commands, implement `run(payload)` in the `.py` file - 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 1. Determine scope and final slash command name. 2. Check whether a command file already exists in that scope. 3. If it exists, load the file first and preserve unknown frontmatter keys. 4. Update YAML config and template/script content. 5. Save the file in the correct scope folder. 6. Report: - the saved config path - the saved content path - the slash command name in `/name` form ## 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.yaml` - `Saved content: /a0/usr/plugins/_commands/commands/explain-code.txt` - `Invoke with: /explain-code`

Frequently asked questions