agent-hierarchy-diagram
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
75
58%
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 ./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 thin on specific capabilities (only one action described) and trigger terms, which could make it harder for Claude to confidently select this skill over alternatives. The 'when' guidance is present but could be more detailed with specific trigger scenarios.
Suggestions
Add more specific concrete actions, e.g., 'Generate visual hierarchy diagrams, map delegation chains, show agent levels and relationships in agent orchestration systems'.
Expand trigger terms to include natural user phrases like 'agent architecture', 'org chart', 'system visualization', 'agent tree', or 'multi-agent structure'.
| 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', 'levels', '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 focus on 'agent system hierarchy diagrams' is fairly specific, but 'documentation or onboarding' is broad and could overlap with other documentation or diagramming skills. The term 'visual hierarchy diagrams' could also conflict with general diagramming skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
50%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 multiple output formats and clear examples. However, it suffers from referencing scripts that don't exist in the bundle, redundant sections (When to Use vs Use Cases), and lacks validation steps for ensuring diagram accuracy. The actionability is weakened by the absence of the actual scripts or inline logic to generate the diagrams.
Suggestions
Either provide the referenced scripts (generate_hierarchy_diagram.sh, generate_mermaid_diagram.sh) in the bundle or include inline logic/code that Claude can execute directly to generate diagrams from agent configuration files.
Merge the 'When to Use' and 'Use Cases' sections to eliminate redundancy and improve conciseness.
Add a validation step: e.g., 'Compare generated diagram against .claude/agents/ directory to verify all agents are represented and levels are correct.'
Provide concrete instructions for how to read agent configuration source files and transform them into the diagram formats, rather than relying on opaque scripts.
| 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 minimal value beyond what's already shown in the examples. Some tightening possible. | 2 / 3 |
Actionability | Provides concrete bash commands and example output formats, but the scripts referenced (generate_hierarchy_diagram.sh, generate_mermaid_diagram.sh) are not provided in any bundle, making the commands not actually executable. The examples are illustrative templates rather than copy-paste-ready tools. | 2 / 3 |
Workflow Clarity | For a relatively simple skill (generate a diagram), the steps are present but loosely organized across sections rather than sequenced. There's no guidance on what to do if scripts fail, how to verify diagram accuracy, or how to update diagrams when the hierarchy changes — missing validation for a documentation-generation task. | 2 / 3 |
Progressive Disclosure | References to external files like /agents/hierarchy.md and .claude/agents/ are mentioned but no bundle files are provided to support them. The content is reasonably structured with clear sections, but the references are unverifiable and the skill could better signal what's in each referenced resource. | 2 / 3 |
Total | 8 / 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-data
- Commit
2dfa65f
- 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.