Agent management
Skill aiskillstore/marketplace/skills/emz1998/agent-management
Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
npx -y skills add aiskillstore/marketplace --skill agent-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.9 KB, 295 tokens by cl100k_base, as published. Nobody here has run it
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/agentsdirectory - 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