agent-management
Use PROACTIVELY this agent when you need to design and create optimal Claude Code subagents, update existing agents with new capabilities, revise agent configurations, analyze project requirements to identify specialized roles, or craft precise agent configurations with appropriate tool permissions and model tiers. When the user specify "Create or Update subagent [name]", this skill must be triggered.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-management/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-management Compares
| Feature / Agent | agent-management | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use PROACTIVELY this agent when you need to design and create optimal Claude Code subagents, update existing agents with new capabilities, revise agent configurations, analyze project requirements to identify specialized roles, or craft precise agent configurations with appropriate tool permissions and model tiers. When the user specify "Create or Update subagent [name]", this skill must be triggered.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
**Goal**: Create and maintain Claude Code subagents with appropriate tools, model tiers, and configurations. **IMPORTANT**: Keep subagent content high-level and concise. Do not dive into implementation details. ## Workflow ### Phase 1: Assessment - Read `.claude/skills/agents-management/references/subagent-doc.md` - Read template at `.claude/skills/agents-management/template.md` - Analyze requirements and identify agent role - Check if agent exists (update vs create) - Determine model tier based on task complexity ### Phase 2: Configuration - Define persona and core responsibilities - Select minimal required tool permissions - Structure workflow phases and constraints - Follow template structure exactly ### Phase 3: Implementation - Write or update agent configuration file - Validate YAML frontmatter and sections - Save it to the appropriate folder in the `.claude/agents` directory - Report completion with agent details and location ## Constraints - No unnecessary tool permissions - No duplicate or conflicting agent roles - Do not overengineer configurations - DO NOT deviate from the template structure ## Acceptance Criteria - Agent file created/updated in `.claude/agents/[team]/` folder - YAML frontmatter includes name, description, tools, model, color - Follows template structure with all required sections - No conflicts with existing agents in the ecosystem - Report delivered with location and usage guidance