command-creator

Automate OpenCode command template creation and management across projects.

1|Updated Jan 27, 2026

Search Tags:#automation #templates #commands #prompts #generate #OpenCode

Ready to run

npx skills add https://github.com/devskale/skale-skills --skill command-creator-devskale

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This skill automates the creation and management of OpenCode commands.

Core Features & Use Cases

Define prompts that run when you type a command in the TUI.
Manage arguments, shell output injection, and file references for reusable automation.
Use cases include building standardized command templates across multiple projects and agents.

Quick Start

Create a command by adding a Markdown file under .opencode/commands/ or configure via opencode.jsonc to register it.

Frequently Asked Questions about command-creator

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

FAQPage Schema

How do I automate repetitive commands across multiple projects?▼

Automate commands by creating reusable templates in .opencode/commands/ or opencode.jsonc. Define prompts, arguments, and file references once, then apply them consistently across projects and agents without manual repetition.

Can I define custom prompts and arguments for OpenCode commands?▼

Yes. Use frontmatter-driven definitions in SKILL.md to specify prompts, manage arguments, inject shell output, and reference files. This lets you build standardized command templates with centralized registration.

What's the best way to create command templates that work across multiple agents?▼

Create command templates by adding Markdown files under .opencode/commands/ or configuring via opencode.jsonc. Centralized registration and frontmatter-driven definitions ensure consistency across projects and multiple agents.

How do I manage file references and shell output in custom commands?▼

Commands support file references and shell output injection through frontmatter definitions. Structure arguments and outputs in your template configuration to enable dynamic, reusable automation tasks.

Can I use assets and references to enhance my command templates?▼

Yes. The Skill supports optional assets and references components alongside frontmatter definitions, enabling richer command templates with supplementary files and documentation for more complex automation scenarios.