create-slash-commands

Create Opencode slash commands with YAML frontmatter and XML-structured bodies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/aaronvstory/taches-oc-prompts-opencode --skill create-slash-commands-aaronvstory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-slash-commands
Source: https://github.com/aaronvstory/taches-oc-prompts-opencode/tree/main/skills/create-slash-commands
Command: npx skills add https://github.com/aaronvstory/taches-oc-prompts-opencode --skill create-slash-commands-aaronvstory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides expert guidance for creating Opencode slash commands, helping teams design, structure, and standardize prompts that trigger reusable workflows within Opencode.

Core Features & Use Cases

  • Frontmatter-driven command design: ensures each command has a mandatory name and description, with optional argument hints and tool restrictions.
  • XML-structured body enforcement: requires sections like <objective>, <process> (or <steps>), and <success_criteria>, plus optional <context>, <verification>, <testing>, and <output> tags.
  • Project and personal command scope: covers both project-local (.config/opencode/commands/) and user-wide (~/.config/opencode/commands/) directories.
  • File naming and invocation: clarifies how command-name.md maps to /command-name and how to reference files or contexts.
  • Generation protocol and best practices: provides a repeatable template approach to create high-quality, safe, and scalable commands.

Quick Start

Create a new command file named <command-name>.md under .config/opencode/commands/ and populate it with YAML frontmatter (name and description) and an XML-structured body.

<quick_start_instruction>Use this process to introduce a new slash command: write the file, ensure frontmatter correctness, and implement the XML body with objective, process, and success criteria.</quick_start_instruction>

Frequently Asked Questions about create-slash-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a custom slash command in Opencode?

To create a custom slash command in Opencode, you create a markdown file named <command-name>.md under .config/opencode/commands/ and populate it with mandatory YAML frontmatter fields alongside a structured XML body.

What structure is required for an Opencode slash command file?

An Opencode slash command requires YAML frontmatter with mandatory name and description fields, plus an XML-structured body containing <objective>, <process> or <steps>, and <success_criteria> tags for consistent workflow execution.

Can I set project-specific versus user-wide Opencode commands?

Yes, you can scope commands project-locally by placing files in .config/opencode/commands/ or user-wide using ~/.config/opencode/commands/ to apply the automated workflows across different working contexts.

How does file naming affect slash command invocation in Opencode?

File naming directly maps to invocation; a markdown file named <command-name>.md will be triggered in Opencode by typing the /command-name syntax, establishing a predictable prompt-engineering workflow.

What optional XML tags can I use when building prompt workflows?

When building prompt workflows, you can include optional XML tags such as <context>, <verification>, <testing>, and <output> alongside the mandatory sections to enrich your slash command automation and validation.

Do I need any external dependencies to define Opencode slash commands?

No, you do not need external dependencies to define Opencode slash commands, as the skill relies entirely on standard markdown formatting, YAML frontmatter, and XML-structured body sections for prompt generation.