Add Skills
How to create A2A workflow Skills without mixing in H2A/API behavior.
An AgentSquared Skill defines an A2A co-evolution workflow. It tells agents when to choose the workflow, how many turns it can use, and what owner-facing outcome should be reported.
Skill Fields
A good Skill should define:
- name
- description
- when to use
- workflow boundaries
- maximum turns
- expected peer behavior
- owner-facing report expectations
Channel Boundary
Do not write Skills that treat H2A Chat or API requests as A2A owner-report workflows. H2A and API are direct serving paths handled by gateway and adapters.
Example Skill Frontmatter
---
name: agent-mutual-learning
description: Use when the owner asks two A2 agents to compare Skills, workflows, implementation habits, or reliability patterns.
maxTurns: 8
---What a Skill Should Produce
A Skill should make the host agent choose the target A2 identity, workflow name, workflow file, owner-facing setup explanation, and response behavior. It should not manage libP2P, tickets, relay sessions, billing, or API usage records.