agent-role-design
Defining what each agent does, knows, and owns in a multi-agent system.
- Installs
- 131
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/ai-design-skills --skill agent-role-design- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads agent-role-design automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Specialist: Deep expertise in one domain. Handles all tasks of a specific type.
- Router: Doesn't do work itself but directs tasks to the right specialist.
- Orchestrator: Manages the overall workflow, coordinates between specialists.
- Validator: Reviews other agents' outputs for quality, safety, or compliance.
- Fallback: Handles cases that other agents can't or won't.
Role Conflicts
When agents' roles overlap or conflict:
- Priority rules: When two agents could handle a task, which one gets it?
- Escalation paths: When agents disagree, who decides?
- Shared resources: When agents need the same data or tools, how is access managed?
- Feedback loops: How do agents inform each other about what they've done?
Design Artefacts
- Agent role cards (one per agent with all specifications)
- Role boundary map showing where each agent's authority starts and stops
- Interaction matrix showing which agents communicate with which
- Authority hierarchy diagram
- Role conflict resolution rules
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 agent-role-design?
Run npx skills add https://github.com/owl-listener/ai-design-skills --skill agent-role-design in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/agent-role-design/ (personal) or .claude/skills/agent-role-design/ (project).
Which AI agents can use agent-role-design?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is agent-role-design safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains agent-role-design?
It is published by owl-listener in owl-listener/ai-design-skills. It has 131 recorded installs.
More from owl-listener/ai-design-skills
system-prompt-structure
owl-listener/ai-design-skills
Anatomy of effective system prompts — role, context, constraints, format.
guardrail-design
owl-listener/ai-design-skills
Open the skill to read its SKILL.md instructions.
constraint-specification
owl-listener/ai-design-skills
Defining output format, length, tone, and content boundaries within prompts.
generative-ui
owl-listener/ai-design-skills
Designing interfaces where AI generates UI components dynamically.
conversation-patterns
owl-listener/ai-design-skills
Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.
progressive-disclosure
owl-listener/ai-design-skills
Revealing AI capability gradually to match user mental models.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available