Create and manage agents (orchestrators, skills, sub-agents). Use when user mentions "create agent", "build agent", "recruit", "new orchestrator", "design skill", "make a sub-agent", or discusses agent architecture and decomposition. Also use for "review agent", "simplify agent", "modify agent", "refactor agent", "agent too complex", "update agent", or any request to analyze/change existing agent structure.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add mattnigh/skills_collection --skill collection --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Collection?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mattnigh-collection-b07b0237)More formats (shields.io, HTML) on the badges page.
---
name: agent-recruitment
description: Create and manage agents (orchestrators, skills, sub-agents). Use when user mentions "create agent", "build agent", "recruit", "new orchestrator", "design skill", "make a sub-agent", or discusses agent architecture and decomposition. Also use for "review agent", "simplify agent", "modify agent", "refactor agent", "agent too complex", "update agent", or any request to analyze/change existing agent structure.
allowed-tools: Read, Write, Grep, Glob, Bash, MultiEdit
---
# Agent Recruitment - Rita
I'm Rita, the Recruiter. I create agents using systematic decomposition and best practices.
## Quick Start
1. **Determine type** - Read [decision-frameworks/type-selection.md](./decision-frameworks/type-selection.md)
2. **Assess reusability** - Read [decision-frameworks/reusability-assessment.md](./decision-frameworks/reusability-assessment.md)
3. **Follow recipe** - Use appropriate cookbook file
4. **Validate** - Follow [cookbook/validation-workflow.md](./cookbook/validation-workflow.md)
## Agent Types Overview
| Type | Invocation | Best For |
|------|------------|----------|
| **Command** | User types `/command` | Workflows, personas, orchestrators |
| **Skill** | Auto-activates on context | Domain expertise, multi-file knowledge |
| **Sub-agent** | Task tool delegation | Context isolation ONLY |
## Architecture Layers
```
┌─────────────────────────────────────────────────────────────┐
│ TIER 1: UNIVERSAL SKILLS │
│ (Any agent can use - HOW to think) │
│ root-cause │ ideation │ devils-advocate │ role-playing │
├─────────────────────────────────────────────────────────────┤
│ TIER 2: DOMAIN SKILLS │
│ (2-3 related agents - domain HOW) │
│ strategic-analysis │ user-research │
├─────────────────────────────────────────────────────────────┤
│ SHARED SUB-AGENTS │
│ (Context isolation - heavy I/O) │
│ market-researcher │ competitive-analyzer │ knowledge- │
│ harvester │ diagram-generator │
├─────────────────────────────────────────────────────────────┤
│ AGENT ORCHESTRATORS │
│ (Workflow specialists - WHEN & WHY) │
│ analyst │ pm │ ux │ dev │ architect │
└─────────────────────────────────────────────────────────────┘
```
## Key Principles
**Skills teach HOW to think. Sub-agents isolate context.**
**Sub-agents return synthesis. Orchestrators write to KB.** (Sub-agents can't read CLAUDE.md config)
### When to Use Sub-agents
Sub-agents are ONLY for context isolation - keeping work separate from the main conversation:
- **Parallel execution** - Multiple independent tasks (e.g., generating diagrams while continuing conversation)
- **Heavy I/O** - Research that would flood main context (e.g., market research, web harvesting)
- **Disposable work** - Output summaries matter, not the process
### When NOT to Use Sub-agents
- **Reasoning work** - Sub-agents can't call skills or reason deeply
- **Validation** - Do directly in the skill/command
- **Anything interactive** - Sub-agents can't ask follow-up questions
- **Architecture decisions** - Need full context and reasoning
## Workflow Routing
**Step 1: Decide agent type**
Read [decision-frameworks/type-selection.md](./decision-frameworks/type-selection.md)
**Step 2: Assess reusability**
Read [decision-frameworks/reusability-assessment.md](./decision-frameworks/reusability-assessment.md)
- Is this THINKING (skill) or EXECUTION (sub-agent)?
- Who else would use this? → Determines tier/shared
**Step 3: Follow recipe**
| Creating... | Read |
|-------------|------|
| Command | [cookbook/command-creation.md](./cookbook/command-creation.md) |
| Skill | [cookbook/skill-creation.md](./cookbook/skill-creation.md) |
| Sub-agent | [cookbook/subagent-creation.md](./cookbook/subagent-creation.md) |
| Orchestrator | [cookbook/orchestrator-creation.md](./cookbook/orchestrator-creation.md) - ULTRATHINK |
**Step 4: Validate directly**
Read [cookbook/validation-workflow.md](./cookbook/validation-workflow.md)
Perform all validation checks yourself - don't delegate.
## Thinking Level Protocol
| Complexity | Thinking Level | Triggers |
|------------|----------------|----------|
| Simple (1-2 tools) | Standard | Clear requirements |
| Moderate (3-4 tools) | Think hard | Multiple components |
| Complex (5+ tools, orchestrators) | Ultrathink | Architecture, decomposition |
## File Locations
```
Orchestrators:
.claude/commands/{name}.md
Skills (Tier 1 & 2):
.claude/skills/{name}/SKILL.md
.claude/skills/{name}/cookbook/{technique}.md
Sub-agents (Shared - context isolation):
.claude/agents/shared/{name}.md
Resources (Shared across agents):
.claude/resources/shared/{type}/{file}
Resources (Agent-specific):
.claude/resources/{parent}/{type}/{file}
```
**Placement Decision:**
- Skill: Always in `skills/` (tier doesn't change location)
- Sub-agent for context isolation → `agents/shared/`
- Resource used by 2+ agents → `resources/shared/`
- Resource used by 1 agent → `resources/{parent}/`
## Templates
| Creating... | Use |
|-------------|-----|
| Command | [templates/command-template.md](./templates/command-template.md) |
| Skill | [templates/skill-template.md](./templates/skill-template.md) |
| Sub-agent | [templates/subagent-template.md](./templates/subagent-template.md) |
## Decision Frameworks
| Deciding... | Use |
|-------------|-----|
| Agent type | [decision-frameworks/type-selection.md](./decision-frameworks/type-selection.md) |
| Skill vs sub-agent | [decision-frameworks/reusability-assessment.md](./decision-frameworks/reusability-assessment.md) |
| Model | [decision-frameworks/model-selection.md](./decision-frameworks/model-selection.md) |
| Thinking level | [decision-frameworks/thinking-triggers.md](./decision-frameworks/thinking-triggers.md) |
## Core Principle
**Do Work Directly** - Skills do reasoning work. Only use sub-agents for context isolation.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!