command-development

Creates standardized Rock and Roll songs with customizable sections and styles.

2|Updated Jun 21, 2019
One-click install
npx skills add https://github.com/helmecke/dotfiles --skill command-development-helmecke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-development
Source: https://github.com/helmecke/dotfiles/tree/main/dot_config/opencode/skill/command-development
Command: npx skills add https://github.com/helmecke/dotfiles --skill command-development-helmecke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing slash commands for OpenCode can be error-prone and inconsistent, so this skill provides a structured framework, frontmatter patterns, and best practices to standardize command creation, documentation, and plugin integration.

Core Features & Use Cases

  • Guidance on YAML frontmatter fields (name, description, model, allowed-tools)
  • Support for dynamic arguments, file references, and Bash execution patterns
  • Clear command organization and plugin integration patterns
  • Comprehensive references and examples for both simple and complex workflows

Quick Start

Create a new slash command file with YAML frontmatter and a prompt body under your project namespace.

Frequently Asked Questions about command-development

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

FAQPage Schema
How do I create slash commands with YAML frontmatter in OpenCode?

To create slash commands in OpenCode, define a command file with YAML frontmatter specifying the name, description, model, and allowed-tools fields, followed by a prompt body. This structure standardizes command creation and enforces consistent frontmatter conventions.

Can I use dynamic arguments and file references in OpenCode slash commands?

Yes, OpenCode slash commands support dynamic arguments, file references, and Bash execution patterns. This allows you to build interactive commands that handle variable inputs and execute shell scripts directly within the command workflow.

What is the best way to organize OpenCode slash commands into plugins?

The best way to organize OpenCode slash commands is by using established plugin patterns and placing command files under your project namespace. This approach ensures clear command organization and seamless plugin integration for both simple and complex workflows.

Does OpenCode slash command development require specific frontmatter fields?

OpenCode slash command development enforces specific YAML frontmatter fields including name, description, model, and allowed-tools. These fields are required to standardize command behavior, control tool access, and maintain consistent documentation across all commands.

Why are my OpenCode slash commands inconsistent across different projects?

OpenCode slash commands become inconsistent without a structured framework for frontmatter patterns and plugin integration. Adopting standardized templates, reusable references, and best practices for command development ensures uniform behavior and documentation across projects.