manage-agents
Creates, modifies, and manages Claude Code subagents by writing agent files with YAML frontmatter, system prompts, and tool configurations. Use when you need to "create an agent", "modify an agent", "set up a specialist", "I need an agent for [task]", "agent to handle [domain]", or "configure agent tools". Covers agent file format, YAML frontmatter, system prompts, tool restrictions, MCP integration, model selection, and testing.
npx skills add majiayu000/claude-skill-registry --skill manage-agents-dawiddutoit-custom-claude --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Manage Agents Create and manage specialized Claude Code subagents with custom capabilities, tool access, and expertise domains. **Use this skill when you need to:** - Create new subagents for specialized tasks - Modify existing agent configurations - Set up domain experts (Python, Neo4j, Testing, etc.) - Configure tool access and MCP server permissions - Understand agent structure and best practices ## Quick Start To create a new agent: 1. **Understand the Need**: What specialized capability or domain expertise is needed? 2. **Choose Location**: Project-level (.claude/agents/) or user-level (~/.claude/agents/) 3. **Define Configuration**: Name, description, model, tools, and permissions 4. **Write System Prompt**: Clear instructions for the agent's specialized role 5. **Test & Validate**: Invoke with @agent-name and verify behavior ## Table of Contents ### Core Sections - [Instructions](#instructions) - [Step 1: Analyze Requirements](#step-1-analyze-requirements) - Determine expertise domain, tool needs, and location - [Step 2: Create Agent File](#step-2-create-agent-file) - Choose project vs user location - [Step 3: Write Agent Configuration](#step-3-write-agent-configuration) -
- Quick Start
- Table of Contents
- Core Sections
- Supporting Resources
- Utility Scripts
- Advanced Topics
- Instructions
- Step 1: Analyze Requirements
- Step 2: Create Agent File
- Step 3: Write Agent Configuration
- Step 4: Configure Tool Access
- Step 5: Configure MCP Access
- Step 6: Select Model
- Step 7: Write System Prompt
Quick test with claude_ask.py python3 .claude/tools/agents/claude_ask.py agent-name "test question" Quiet mode (just the answer) python3 .claude/tools/agents/claude_ask.py -q agent-name "test question" JSON output for validation python3 .claude/tools/agents/claude_ask.py --json agent-name "test question" With timeout for complex tasks python3 .claude/tools/agents/claude_ask.py agent-name "complex task" --timeout 120 cd /Users/dawiddutoit/projects/play/temet-run/.claude uv sync --extras mcp # Install MCP dependencies (if not already done)
What does the manage-agents skill do?
Creates, modifies, and manages Claude Code subagents by writing agent files with YAML frontmatter, system prompts, and tool configurations. Use when you need to "create an agent", "modify an agent", "set up a specialist", "I need an agent for [task]", "agent to handle [domain]", or "configure agent tools". Covers agent file format, YAML frontmatter, system prompts, tool restrictions, MCP integration, model selection, and testing.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill manage-agents-dawiddutoit-custom-claude --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.