agent-builder

Create OpenCode agents following best practices and configuration standards.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/cc01cc/cmtx-project --skill agent-builder-cc01cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-builder
Source: https://github.com/cc01cc/cmtx-project/tree/main/.opencode/skills/agent-builder
Command: npx skills add https://github.com/cc01cc/cmtx-project --skill agent-builder-cc01cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured guide for creating OpenCode agents that follow best practices and configuration standards, helping teams standardize agent design and governance.

Core Features & Use Cases

  • Agent taxonomy: explain primary agents and subagents, roles, and use-case scenarios.
  • Configuration structure: describe file locations, front matter fields, and system prompts.
  • Best practices: outline permission defaults, governance, naming conventions, and safety considerations.

Quick Start

Follow the OpenCode CLI recommendation to create a new agent definition file and populate metadata according to the provided template.

Frequently Asked Questions about agent-builder

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

FAQPage Schema
How do I create OpenCode agents that follow configuration standards?

Creating OpenCode agents requires defining agent definition files with proper front matter metadata and system prompts. You populate file locations and configuration structures following standardized templates for reliable deployment across projects.

What is the difference between primary agents and subagents in OpenCode?

Primary agents and subagents in OpenCode differ by their designated roles and use-case scenarios. The agent taxonomy distinguishes them to structure deployment workflows, ensuring each agent type handles appropriate tasks within standardized governance frameworks.

How do I configure permissions for OpenCode agents?

Configuring OpenCode agent permissions involves setting permission defaults within agent definition files. Best practices outline specific governance and safety considerations to control access, ensuring reliable and standardized agent workflows across team projects.

What naming conventions should I use for OpenCode agents?

Naming conventions for OpenCode agents follow standardized best practices outlined in configuration guides. Consistent naming ensures reliable deployment and clear governance across projects, helping teams maintain structured agent workflows and predictable system behavior.

Can I use OpenCode agents for standardized workflows across multiple projects?

OpenCode agents support standardized workflows across multiple projects through consistent configuration structures and governance practices. Teams implement these agents to ensure reliable deployment, maintaining uniform permission systems and naming conventions throughout different project environments.

When do I need to define agent taxonomy in OpenCode configuration?

Defining agent taxonomy in OpenCode configuration is needed when implementing standardized agent workflows across projects. It clarifies primary agents versus subagents, their specific roles, and use-case scenarios to ensure consistent governance and reliable deployment.