zeus-commands

Create and manage custom slash commands with YAML frontmatter in OpenCode.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/Aveer/OpenZeus --skill zeus-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeus-commands
Source: https://github.com/Aveer/OpenZeus/tree/main/skills/zeus-commands
Command: npx skills add https://github.com/Aveer/OpenZeus --skill zeus-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining inconsistent or undocumented automation workflows by providing a structured framework for creating, managing, and executing custom slash commands within the OpenCode environment.

Core Features & Use Cases

  • Template-Driven Creation: Utilize standardized patterns to build commands that handle arguments, shell output injection, and file content inclusion.
  • Workflow Automation: Quickly turn repetitive terminal tasks or complex prompt sequences into reusable slash commands.
  • Use Case: A developer can create a custom command to automate the generation of release notes by injecting git log output and file summaries directly into a prompt template.

Quick Start

Use the zeus-commands skill to generate a new command template for automating your daily git status reporting.

Frequently Asked Questions about zeus-commands

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

FAQPage Schema
How do I automate repetitive terminal tasks by creating custom slash commands?

Automate repetitive terminal tasks by using a structured framework to create custom slash commands that incorporate shell output, file content, and positional arguments into standardized prompt templates. This enforces consistent workflows.

What is the best way to standardize and manage prompt templates for workflow automation?

Standardize prompt templates by adhering to a defined YAML frontmatter schema and command directory structure, ensuring proper TUI integration and consistent management of custom OpenCode commands.

Can I inject shell output and file content directly into a custom command template?

Yes, you can inject shell output and file content directly into custom command templates. This allows you to automate complex tasks like generating release notes from git log output and file summaries.

Does the OpenCode workspace require a specific directory structure for custom commands?

The OpenCode workspace requires a specific command directory structure and YAML frontmatter schema for custom commands. Adhering to this structure ensures proper TUI integration and successful command execution.

Why do I need YAML frontmatter to create custom slash commands in OpenCode?

You need YAML frontmatter to define the metadata and configuration of custom slash commands. This standardization ensures the prompt templates integrate correctly with the OpenCode TUI and execute repetitive tasks reliably.

Are there limitations when using positional arguments in OpenCode command templates?

Positional arguments in OpenCode command templates require strict adherence to the YAML frontmatter schema to function properly. Limitations arise if the command directory structure is not correctly configured for TUI integration.