Agent Role Design

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

207 stars 37 forksAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/ai-design-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/ai-design-skills --skill agent-role-design
Manual install
git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git /tmp/ai-design-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ai-design-skills/claude-plugin/design-agent-orchestration/skills/agent-role-design ~/.claude/skills/agent-role-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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.
## Role Patterns
Read the full skill on GitHub

Details

Skill name
agent-role-design
Path
claude-plugin/design-agent-orchestration/skills/agent-role-design/SKILL.md
License
MIT
Repo updated
9 June 2026

FAQ

What does the Agent Role Design skill do?

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

How do I install the Agent Role Design skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/ai-design-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Agent Role Design popular?

It lives in Owl-Listener/ai-design-skills, which has 207 GitHub stars and 37 forks.

Related skills

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.