command-creator

Create custom OpenCode commands with frontmatter metadata and prompt templates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/acedergren/oci-self-service-portal --skill command-creator-acedergren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-creator
Source: https://github.com/acedergren/oci-self-service-portal/tree/main/.opencode/skills/command-creator
Command: npx skills add https://github.com/acedergren/oci-self-service-portal --skill command-creator-acedergren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode users often duplicate prompts and boilerplate prompts across projects. This skill provides a straightforward mechanism to define reusable commands that encapsulate prompt templates and frontmatter metadata, enabling consistent automation workflows.

Core Features & Use Cases

  • Create per-project or global command definitions in Markdown or JSON, including frontmatter metadata and a reusable prompt template.
  • Organize commands under .opencode/commands and reuse across teams to accelerate prompt-driven automation.
  • Extend OpenCode workflows by injecting file contents and shell outputs into prompts to tailor AI behavior.

Quick Start

Create a new command by adding a Markdown file to .opencode/commands (e.g., .opencode/commands/test.md) and define its frontmatter and template.

Frequently Asked Questions about command-creator

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

FAQPage Schema
How do I create reusable OpenCode commands to automate repetitive prompts?

You can create reusable OpenCode commands by defining Markdown or JSON files with frontmatter metadata and prompt templates under the .opencode/commands directory. This encapsulates your prompts for consistent, automated AI interactions across projects.

What is the best way to organize custom commands for my development team?

Organize custom commands by placing Markdown or JSON definitions under .opencode/commands. You can define commands per-project or globally, enabling your team to reuse standardized prompt templates and accelerate prompt-driven automation workflows.

Does OpenCode command creation require specific frontmatter metadata?

Yes, OpenCode command creation requires frontmatter metadata, specifically validating the required name and description fields. This frontmatter-driven metadata ensures commands are properly documented and consistently structured for AI interactions.

Can I inject file contents and shell outputs into my OpenCode prompt templates?

Yes, you can extend OpenCode workflows by injecting file contents and shell outputs directly into your prompt templates. This allows you to tailor AI behavior dynamically based on contextual project data.

How do I define global versus per-project automation commands in OpenCode?

You define per-project commands by adding Markdown or JSON files to the .opencode/commands directory within your project, while global command definitions are structured similarly but stored globally to reuse across all team projects.

What are the limitations when defining custom commands in Markdown versus JSON?

Both Markdown and JSON definitions support frontmatter metadata and reusable prompt templates. Markdown files allow template-driven prompt structures directly, while JSON provides structured definitions; both are validated for required name and description frontmatter.