open-gitagent/opengap / examples/gitagent-helper/skills/create-agent
create-agent
UnverifiedCreates and configures agent.yaml files, writes SOUL.md personality definitions, and sets up agent directory structures with skills, tools, and knowledge. Use when the user wants to configure an agent, create agent.yaml, write SOUL.md, set up agent directory structure, or customize agent settings.
Create & Configure Agents
Quick Start
- Create directory structure:
mkdir -p my-agent/skills - Write
agent.yamlwith required fields (see below) - Create
SOUL.mdwith agent identity - Add skills, tools, and knowledge as needed
- Validate:
opengap validate -d ./my-agent
agent.yaml Reference
Required Fields
spec_version: "0.1.0"
name: my-agent # Unique identifier
version: 1.0.0 # Semantic version
description: What this agent does
Model Configuration
model:
preferred: claude-sonnet-4-5-20250929
fallback:
- claude-haiku-4-5-20251001
constraints:
temperature: 0.2 # 0.0 - 1.0
max_tokens: 4096
top_p: 0.9
Skills & Tools
skills:
- code-review # Must match directory name in skills/
- security-audit
tools:
- lint-check # Must match filename in tools/ (without .yaml)
Runtime
runtime:
max_turns: 20 # Max conversation turns
timeout: 120 # Seconds
Sub-Agents
agents:
reviewer:
description: Reviews code quality
delegation:
mode: auto
triggers:
- "review this"
Writing a Good SOUL.md
A SOUL.md should have these sections:
- Core Identity — Who is this agent? One clear sentence.
- Communication Style — How does it talk? (direct, friendly, formal, etc.)
- Values & Principles — What does it prioritize?
- Domain Expertise — What does it know?
- Collaboration Style — How does it work with the user?
Writing RULES.md
Structure as:
- Must Always — Non-negotiable behaviors
- Must Never — Hard boundaries
- Output Constraints — Formatting rules
- Interaction Boundaries — Scope limits
Adding Skills
Create skills/<name>/SKILL.md:
---
name: my-skill
description: What this skill does
license: MIT
allowed-tools: Read Edit Grep
metadata:
version: "1.0.0"
---
# Instructions
[Detailed instructions for using this skill]
Adding Tools
Create tools/<name>.yaml:
name: my-tool
description: What this tool does
input_schema:
type: object
properties:
query:
type: string
description: Search query
required:
- query
Adding Knowledge
Create knowledge/index.yaml:
documents:
- path: reference.md
always_load: true # Include in system prompt
- path: appendix.md
always_load: false # Available on demand
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |