command-authoring

Automate creation and governance of OpenCode custom slash commands.

1|Updated Jun 1, 2025

Search Tags:#templates #consistency #command #authoring #frontmatter #opencode #slash-command

Ready to run

npx skills add https://github.com/rcdailey/dotfiles --skill command-authoring-rcdailey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: command-authoring
Source: https://github.com/rcdailey/dotfiles/tree/main/home/dot_config/opencode/exact_skills/command-authoring
Command: npx skills add https://github.com/rcdailey/dotfiles --skill command-authoring-rcdailey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Command authoring for OpenCode often lacks standardization, leading to inconsistent frontmatter, arguments, routing, and permissions across projects. This skill provides conventions and patterns to create, edit, and review custom slash commands reliably.

Core Features & Use Cases

Standardizes command frontmatter fields (name, description, agent, model, subtask) and file placement.
Provides templates and patterns for command files within local and project repositories.
Reduces drift during command creation and review, enabling safer, faster deployment.

Quick Start

Create a new command file at ~/.config/opencode/commands/<name>.md and implement the frontmatter and body following the OpenCode conventions.

Frequently Asked Questions about command-authoring

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

FAQPage Schema

How do I create custom OpenCode slash commands with consistent frontmatter?▼

To create custom OpenCode slash commands, add a Markdown file at ~/.config/opencode/commands/<name>.md and define standard frontmatter fields including name, description, agent, model, and subtask to ensure schema consistency.

What frontmatter fields are required for OpenCode custom command files?▼

OpenCode custom command files require frontmatter fields for name, description, agent, model, and subtask. Enforcing this schema ensures proper command routing, permissions, and consistent execution across local and shared repositories.

Where should I place OpenCode slash command files for global versus project-specific use?▼

OpenCode supports per-project and global command locations. Place global command files in ~/.config/opencode/commands/<name>.md, while project-specific commands reside within the shared repository structure for team access.

What is the best way to standardize slash command authoring across a development team?▼

Standardize slash command authoring by applying a template structure that enforces frontmatter schema, agent routing, and permissions across local machines and shared repositories, reducing drift during command creation and review.

Can I configure agent routing and model selection within OpenCode command frontmatter?▼

Yes, OpenCode command frontmatter supports agent routing and model selection directly within the file header. Specifying the agent and model fields ensures commands execute using the correct execution context and permissions.

Why does my OpenCode custom command fail to execute properly?▼

OpenCode custom commands often fail due to inconsistent frontmatter schema, missing required fields like name or agent, or incorrect file placement outside the expected local or project command directory structures.