skills.rest
nullhack
nullhackCOMMUNITY
Explore all skills by this author →
GitHub

create-agent

Create OpenCode agents with standardized YAML frontmatter and directory templates.

Updated Apr 17, 2026
Search Tags:#automation#templates#workflows#opencode#yaml-frontmatter#agent-design#create-agent
One-click install
npx skills add https://github.com/nullhack/pytest-beehave --skill create-agent-nullhack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-agent
Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/create-agent
Command: npx skills add https://github.com/nullhack/pytest-beehave --skill create-agent-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create new OpenCode agents with research-backed design patterns and industry standards to ensure consistent agent architecture and governance across projects.

Core Features & Use Cases

  • Define agent ownership, instruction patterns, and tool surfaces to avoid scope creep.
  • Provide templates and examples to accelerate agent creation and governance.
  • Use across teams to standardize agent production, review, and deployment.

Quick Start

Create a new agent file under .opencode/agents/ using the provided template and frontmatter.

Frequently Asked Questions about create-agent

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

FAQPage Schema
How do I create OpenCode agents with standardized YAML frontmatter?▼

Create an OpenCode agent by placing a new file under .opencode/agents/ using provided templates and YAML frontmatter. This enforces consistent directory structure, governance, and reuse across automation workflows.

When do I need a separate OpenCode agent for my workflows?▼

You need a separate OpenCode agent when a distinct ownership domain, instruction surface, or approval policy requires isolation. This separation guides agent creation, structure, and governance to avoid scope creep.

How do I design agent ownership and tool surfaces to avoid scope creep?▼

Design agent ownership and tool surfaces by applying research-backed design patterns and industry standards. Defining these boundaries standardizes agent production and enforces governance across project workflows.

Does this approach work for standardizing agent production across teams?▼

Yes, this approach standardizes agent production across teams by enforcing standardized YAML frontmatter, agent file templates, and directory structure. This ensures consistent discovery, review, and deployment governance.

What is the best way to structure OpenCode agent files for consistent discovery?▼

The best way to structure OpenCode agent files is using a standardized directory structure under .opencode/agents/ with YAML frontmatter. This research-backed pattern accelerates creation and ensures consistent reuse.

Related Skills

Explore More Software Engineering Skills→
darellchua2darellchua2
4

opencode-agent-creation

Generate OpenCode agent configurations as JSON or Markdown with frontmatter.

Community
Basic
borealBytesborealBytes
7

technical-documentation

Audit and align repository governance files and documentation across agent workflows.

Community
Advanced
ZESCODEZESCODE

ZES-verification-before-completion

Validate task completion via multi-agent tests, linting, and requirement checks.

Community
Advanced
docs-plusdocs-plus
88

scaffold-exercises

Generate standardized exercise directory structures with required subfolders and stub files.

Official
Intermediate