opencode-command-authoring

Create, validate, and execute OpenCode command definitions with standardized frontmatter.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill opencode-command-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-command-authoring
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/opencode-command-authoring
Command: npx skills add https://github.com/open-hax/opencode-skills --skill opencode-command-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage OpenCode command definitions with valid frontmatter and consistent execution.

Core Features & Use Cases

  • Automated scaffolding: generate command files with proper frontmatter and structure.
  • Command discovery & execution: list available commands and run them via the OpenCode runner.
  • Use Case: Rapidly bootstrap new commands for automation tasks in CI/CD or local tooling.

Quick Start

Create a new command by running the command-authoring tool to generate a compliant file in .opencode/command.

Frequently Asked Questions about opencode-command-authoring

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

FAQPage Schema
How do I automate scaffolding for OpenCode command files with valid frontmatter?

Automating OpenCode command scaffolding generates compliant files with standardized frontmatter in the .opencode/command directory, ensuring correct structure and validity for repeatable developer workflows.

What is the best way to list and execute available OpenCode commands across projects?

Listing and executing OpenCode commands is handled by registering commands via bin scripts and running them through the OpenCode runner, ensuring deterministic behavior across different projects.

How do I validate OpenCode command frontmatter to prevent runtime execution errors?

Validating OpenCode command frontmatter checks the generated command definitions against standardized schemas before execution, preventing runtime errors and ensuring deterministic run behavior.

Can I use command definitions to bootstrap CI/CD automation tasks locally?

Command definitions can bootstrap CI/CD automation tasks locally by generating repeatable command scaffolding, allowing rapid creation and execution of tooling scripts through the OpenCode runner.

Do I need bin scripts to register OpenCode commands for execution?

You need bin scripts to register OpenCode commands, as the registration process relies on these scripts to enable command discovery and deterministic execution through the OpenCode runner.