agent-hierarchy-diagram
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
77
62%
Does it follow best practices?
Impact
85%
1.39xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agent/agent-hierarchy-diagram/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description adequately communicates the core purpose and includes an explicit 'Use for' clause, which is good. However, it is somewhat narrow in specificity (only one action described) and the trigger terms could be broader to capture more natural user phrasings. The 'when' triggers of 'documentation or onboarding' are overly broad and could cause conflicts with other skills.
Suggestions
Add more specific concrete actions beyond just 'generate diagrams', e.g., 'Generate visual hierarchy diagrams of agent systems, map delegation chains, and visualize multi-level agent architectures'.
Expand trigger terms to include natural variations users might say, such as 'agent architecture', 'agent tree', 'system visualization', 'org chart', or 'agent topology'.
Narrow the 'when' clause to be more specific, e.g., 'Use when the user asks to visualize agent hierarchies, map delegation structures, or create architecture diagrams for multi-agent systems'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('agent system') and a specific action ('generate visual hierarchy diagrams showing levels and delegation'), but only describes one core action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Answers both 'what' (generate visual hierarchy diagrams of agent system showing levels and delegation) and 'when' (use for documentation or onboarding), though the 'when' clause is brief, it is explicitly stated. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'hierarchy diagrams', 'agent system', 'delegation', 'documentation', and 'onboarding', but misses common variations users might say such as 'org chart', 'architecture diagram', 'agent tree', 'visualization', or 'system overview'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'agent system' and 'hierarchy diagrams' is somewhat distinctive, but 'documentation' and 'onboarding' are very broad triggers that could overlap with many other skills. The term 'visual' could also conflict with general diagramming or visualization skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable overview of generating agent hierarchy diagrams with good structure and clear formatting examples. However, it suffers from relying on scripts that may not exist without explaining how to create them, has redundant sections (When to Use vs Use Cases), and lacks a validation workflow to ensure diagram accuracy. The content would benefit from either including the script contents or providing inline executable approaches.
Suggestions
Either include the script contents or provide inline executable code (e.g., a Python script that reads agent configs and generates the diagram) so the skill is truly actionable without external dependencies.
Merge 'When to Use' and 'Use Cases' sections to eliminate redundancy and improve conciseness.
Add a validation step to the workflow, e.g., 'After generating, compare against .claude/agents/ directory to verify all agents are represented' to create a feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — the 'Use Cases' section largely repeats the 'When to Use' section, and the 'Output Formats' section adds little value beyond what's already shown in the examples. Some tightening possible. | 2 / 3 |
Actionability | Provides concrete script commands and example output formats, but the scripts referenced (generate_hierarchy_diagram.sh, generate_mermaid_diagram.sh) are assumed to exist without any guidance on creating them or what they contain. The examples are illustrative but not truly executable — they're static output samples rather than copy-paste-ready code to generate diagrams. | 2 / 3 |
Workflow Clarity | For a relatively simple skill, the steps are present (run script, save output) but there's no validation step — no way to verify the diagram is accurate or complete. The reference to 'agent-test-delegation' for validation is mentioned but not integrated into a workflow sequence. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, appropriate length for a SKILL.md, and references to external files are one level deep and clearly signaled. The structure flows logically from quick reference to formats to references. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- majiayu000/claude-skill-registry
- Commit
632759f
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.