Menu

Individual skill

agent-role-design

0upvotes

Defining what each agent does, knows, and owns in a multi-agent system.

gemini-extension/design-agent-orchestration/skills/agent-role-design/SKILL.md

Read pinned source

Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
204
Repository last updated
Jun 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Agent Role Design
In a multi-agent system, each agent needs a clearly defined role — what it does, what it knows, what it's responsible for, and where its authority ends. Without clear roles, agents duplicate work, conflict with each other, or leave gaps.
## Defining an Agent Role
For each agent in the system, specify:
- **Purpose**: What is this agent for? One sentence describing its reason to exist.
- **Capabilities**: What can this agent do? List specific actions and outputs.
- **Knowledge scope**: What does this agent know about? What domains, data, and context does it have access to?
- **Authority**: What decisions can this agent make autonomously? What requires approval?
- **Boundaries**: What is explicitly outside this agent's scope? Where does it stop and hand off?
- **Success criteria**: How do you know this agent is doing its job well?
## Role Design Principles
- **Single responsibility**: Each agent should have one clear purpose. If you need a paragraph to explain what it does, it's doing too much.
- **Clear boundaries**: The line between one agent's scope and another's should be unambiguous. No overlapping authority without explicit conflict resolution.
- **Minimal coupling**: Agents should be able to do their work with minimal dependencies on other agents. Share results, not process.
- **Appropriate autonomy**: The level of autonomous decision-making should match the stakes and the agent's reliability in that domain.
Back to top