Agent Hierarchy Diagram Skill for Claude
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/majiayu000/claude-skill-registry --skill agent-hierarchy-diagramWhat comes with it
836 bytes besides the instructionThe instruction itself
8 sections, as written by the authorAgent Hierarchy Diagram
Generate visual diagrams showing agent system structure and relationships.
When to Use
- Documenting agent system for team
- Understanding delegation structure
- Onboarding new contributors
- Visualizing agent relationships for presentations
Quick Reference
# Generate ASCII tree diagram
./scripts/generate_hierarchy_diagram.sh
# Generate Mermaid diagram
./scripts/generate_mermaid_diagram.sh > hierarchy.mmd
# Save to documentation
./scripts/generate_hierarchy_diagram.sh > agents/hierarchy-visual.txt
ASCII Tree Format
Chief Architect (L0)
├── Foundation Orchestrator (L1)
│ ├── Repository Design (L2)
│ │ ├── Directory Specialist (L3)
│ │ │ └── Junior Engineer (L5)
│ │ └── Config Specialist (L3)
│ └── Config Design (L2)
├── Shared Library Orchestrator (L1)
│ └── Tensor Module Design (L2)
│ └── Tensor Specialist (L3)
└── Tooling Orchestrator (L1)
Mermaid Format
graph TD
A[Chief Architect L0] --> B[Foundation Orchestrator L1]
B --> C[Repository Design L2]
C --> D[Directory Specialist L3]
D --> E[Junior Engineer L5]
Use Cases
- Add to
/agents/hierarchy.mdfor reference - Include in onboarding documentation
- Create presentation materials
- Understand delegation chains
- Communicate structure to stakeholders
Output Formats
ASCII: Human-readable in terminals, copy-pasteable in docs
Mermaid: Renders in GitHub markdown, editable in Mermaid editor
GraphML: Import into diagram tools (yEd, Graphviz)
References
/agents/hierarchy.md- Existing hierarchy documentationagent-test-delegation- Validate diagram accuracy.claude/agents/- Agent configuration source
Other skills for the same job
different authors, same section of the catalogue
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.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take majiayu000/agent-hierarchy-diagram from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.