command-creator

Name: command-creator
Availability: InStock
Author: patrickhaahr

Create reusable Opencode commands with frontmatter and Markdown prompt bodies.

Updated Jun 15, 2025

Search Tags:#automation #markdown #cli #frontmatter #opencode #prompt-engineering #custom-commands

Ready to run

npx skills add https://github.com/patrickhaahr/dotfiles --skill command-creator-patrickhaahr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: command-creator
Source: https://github.com/patrickhaahr/dotfiles/tree/main/opencode/.config/opencode/skills/command-creator
Command: npx skills add https://github.com/patrickhaahr/dotfiles --skill command-creator-patrickhaahr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to define and manage reusable commands for Opencode, reducing repetitive prompt setup and ensuring consistent behavior across projects.

Core Features & Use Cases

Define global or project-scoped commands using Markdown files in the command/ directory.
Customize each command with frontmatter options (description, agent, model, subtask) to tailor behavior.
Use case: rapidly create and reuse prompts for common workflows across teams and projects.

Quick Start

Create a new Markdown file named <name>.md under ~/.config/opencode/command/ or .opencode/command/ with the appropriate frontmatter and a prompt body. The filename becomes the command name, and the frontmatter defines how it runs. Then you can invoke it from the TUI with /<name>.

Frequently Asked Questions about command-creator

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

FAQPage Schema

How do I create custom Opencode commands to automate repetitive prompts?▼

To create custom Opencode commands, add a Markdown file named <name>.md under the command/ directory. Define frontmatter fields like name, description, agent, and model, then write your prompt body to automate the task.

What frontmatter fields are required to configure an Opencode command?▼

Configuring an Opencode command requires defining frontmatter fields including name, description, agent, and model. These fields tailor the command behavior alongside a Markdown body that serves as the prompt runtime.

Can I define global Opencode commands for reuse across multiple projects and teams?▼

Yes, you can define global Opencode commands by placing Markdown files in the ~/.config/opencode/command/ directory. Project-scoped commands go in .opencode/command/ to ensure consistent behavior across specific projects.

How do I invoke a custom Markdown command from the Opencode TUI?▼

You invoke a custom command from the Opencode TUI by typing /<name>. The filename of your Markdown file in the command directory automatically becomes the command name used for invocation.

What is the best way to standardize prompt engineering workflows for repetitive tasks?▼

The best way to standardize prompt engineering workflows is creating reusable Opencode commands. By defining standardized prompts in Markdown files with specific frontmatter, teams ensure consistent behavior across multiple projects.

Do I need any dependencies to set up prompt automation with Opencode?▼

No dependencies are required to set up prompt automation. You only need to create Markdown files with appropriate frontmatter configuration in the designated command directories to start automating tasks.