add a0-new-agent agent profile creation Skill
Adds a guided wizard for creating Agent Zero profiles covering scope selection (user / plugin-distributed / project-scoped), the agent.yaml schema, the prompt inheritance model, and optional profile-specific tools and extensions. Leads with agent.system.main.specifics.md as the canonical override slot — the file ships empty by design and every profile under /a0/agents/ overrides it — with pointers to the developer, hacker, researcher, agent0, and _example profiles as reference shapes. Also cross-links the new skill from a0-development under "Creating Agent Profiles" so users land on the wizard from the broader framework guide.
Alessandro committed
Apr 21, 2026 at 05:51 UTC
d90cb36898150b6dcd5df93f120d955389e02358
1 file changed
+32
-10
skills/a0-new-agent/SKILL.md
+32
-10
@@ -82,19 +82,25 @@ A profile with only `agent.yaml` is valid — it inherits everything from `defau
82
83
## Step 3: Override prompts (the most common customization)
84
85
-Profiles inherit all prompts from `/a0/prompts/default/` and from `/a0/agents/default/prompts/`. To change behavior, drop a file with the **same filename** into `<PROFILE_ROOT>/<name>/prompts/`. The loader searches profile-specific prompts first, then falls back.
85
+Profiles inherit all prompts from `/a0/prompts/` and from `/a0/agents/default/`. To change behavior, drop a file with the **same filename** into `<PROFILE_ROOT>/<name>/prompts/`. The loader searches profile-specific prompts first and falls back to the defaults.
86
87
-The usual overrides:
87
+### The canonical override: `agent.system.main.specifics.md`
88
89
-| File | What it controls |
89
+This is the designated extension slot for profile-specific role, identity, and behavior instructions. The file ships **empty** in both `/a0/prompts/agent.system.main.specifics.md` and `/a0/agents/default/agent.system.main.specifics.md` precisely so profiles can fill it in without fighting the base prompt. It is included from `agent.system.main.md` right after `agent.system.main.role.md`, so whatever you put here layers on top of the inherited role.
90
+
91
+**Every shipped profile in `/a0/agents/` overrides this file** — a good sanity check that this is the right place for your specialization. Look at the existing profiles for concrete shape:
92
+
93
+| Profile | What its `agent.system.main.specifics.md` does |
94
|---|---|
91
-| `agent.system.main.role.md` | The agent's role / identity (most common) |
92
-| `agent.system.main.specifics.md` | Specialized behavioral instructions for this profile |
93
-| `agent.system.main.communication.md` | Communication style / reply format |
94
-| `agent.system.main.environment.md` | Environment & tooling context (e.g. `hacker` uses this for Kali) |
95
-| `agent.system.tool.<name>.md` | Usage instructions for a profile-specific tool |
95
+| `/a0/agents/agent0/prompts/agent.system.main.specifics.md` | Establishes the top-level user-facing agent's behavior |
96
+| `/a0/agents/developer/prompts/agent.system.main.specifics.md` | Full "Master Developer" role + process spec (most elaborate example) |
97
+| `/a0/agents/hacker/prompts/agent.system.main.specifics.md` | Concise red/blue team pentester identity |
98
+| `/a0/agents/researcher/prompts/agent.system.main.specifics.md` | Research methodology and deliverable expectations |
99
+| `/a0/agents/_example/prompts/agent.system.main.specifics.md` | Minimal demo override (fictional "Agent Zero" persona) |
100
97
-Example `agent.system.main.role.md`:
101
+Start by copying whichever existing profile's `specifics.md` is closest to your target, then rewrite.
102
+
103
+Example `agent.system.main.specifics.md` for a data analyst:
104
105
```markdown
106
## Your role
@@ -106,10 +112,26 @@ Your expertise includes:
112
- Statistical modeling and hypothesis testing
113
- SQL queries and database analysis
114
- Data cleaning and preprocessing
115
+
116
+## Process
117
+1. Understand the data and the question
118
+2. Choose appropriate tools and methods
119
+3. Execute analysis with `code_execution_tool`
120
+4. Visualize results when applicable
121
+5. Provide clear interpretation of findings
122
```
123
124
+### Secondary overrides (use only when needed)
125
+
126
+| File | When to override | Shipped example |
127
+|---|---|---|
128
+| `agent.system.main.role.md` | Replace the base role framing wholesale (rare — most profiles layer via `specifics.md` instead) | `/a0/agents/agent0/prompts/agent.system.main.role.md` |
129
+| `agent.system.main.communication.md` | Change reply format / communication style | `/a0/agents/developer/prompts/agent.system.main.communication.md`, `/a0/agents/researcher/prompts/...` |
130
+| `agent.system.main.environment.md` | Describe a non-default runtime environment | `/a0/agents/hacker/prompts/agent.system.main.environment.md` (Kali/Docker) |
131
+| `agent.system.tool.<name>.md` | Document a profile-specific tool (see Step 4) | `/a0/agents/_example/prompts/agent.system.tool.example_tool.md` |
132
+
133
> [!TIP]
112
-> Only override what you need. Copying unchanged prompt files creates drift when the framework updates the originals.
134
+> Only override what you actually need to change. Copying unchanged prompt files creates silent drift when the framework updates the originals — `specifics.md` is safe to own because its default is empty by design.
135
136
---
137