agent-development

Translate user requirements into OpenCode agent configurations with frontmatter and tool scoping.

2|Updated Jun 21, 2019
One-click install
npx skills add https://github.com/helmecke/dotfiles --skill agent-development-helmecke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-development
Source: https://github.com/helmecke/dotfiles/tree/main/dot_config/opencode/skill/agent-development
Command: npx skills add https://github.com/helmecke/dotfiles --skill agent-development-helmecke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode users often struggle to design consistent, production-ready agent configurations. This skill streamlines translating user requirements into fully specified agent definitions, ensuring consistent naming, frontmatter, triggering patterns, and safety considerations.

Core Features & Use Cases

  • Generates complete agent metadata from user prompts, including identifier, triggering conditions, system prompts, tools, permissions, and output formats.
  • Enforces CLAUDE.md-aligned structure and OpenCode frontmatter rules to ensure compatibility and auto-discovery.
  • Validates safety and quality constraints (no toxic content, appropriate tool access, explicit edge-case handling).

Quick Start

Describe your agent requirements to Claude and generate a production-ready agent file.

Frequently Asked Questions about agent-development

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

FAQPage Schema
How do I create a production-ready OpenCode agent configuration with proper frontmatter?

Generate a production-ready OpenCode agent configuration by providing your requirements, which produces structured frontmatter, system prompts, tool permissions, and validation checks for auto-discovery.

What is the best way to structure system prompts and tool permissions for OpenCode agents?

The best way to structure system prompts and tool permissions is using CLAUDE.md-aligned rules, ensuring clear scoping, safe defaults, and explicit edge-case handling for agent safety and quality.

Do I need to follow specific validation rules when generating an OpenCode agent?

Yes, you need to follow validation rules that enforce safety and quality constraints, ensuring no toxic content, appropriate tool access, and structured frontmatter aligned with CLAUDE.md contexts.

Can I use my own triggering conditions and output formats for OpenCode agent generation?

Yes, you can use your own triggering conditions and output formats. Agent generation applies to explicit requests, proactive triggering, and edge cases across multiple project contexts.

Why does my OpenCode agent fail auto-discovery despite having frontmatter?

Auto-discovery fails when frontmatter lacks CLAUDE.md-aligned structure or OpenCode rules. Ensure your configuration includes consistent naming, explicit triggering patterns, and validated safety constraints.