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 describing capabilities (only one action) and the trigger terms could be more comprehensive to cover natural user language variations. The 'when' triggers of 'documentation or onboarding' are overly broad and could cause false matches.
Suggestions
Add more specific trigger terms users might naturally say, such as 'agent architecture', 'system visualization', 'org chart', 'delegation tree', or 'agent topology'.
Narrow the 'Use for' clause to be more specific, e.g., 'Use when the user asks to visualize agent hierarchies, map delegation chains, or understand multi-agent system structure' rather than the generic 'documentation or onboarding'.
| 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 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.
The skill provides a reasonable overview of generating agent hierarchy diagrams with good structure and clear formatting examples. However, it suffers from redundancy between sections, relies on scripts that may not exist without explaining how to create them, and lacks a clear end-to-end workflow with validation steps. The content would benefit from consolidation and more actionable, self-contained guidance.
Suggestions
Merge the overlapping 'When to Use' and 'Use Cases' sections into a single concise section to eliminate redundancy.
Either include the script contents inline or provide instructions for generating diagrams without the scripts (e.g., a Python snippet that reads agent configs and outputs the tree).
Add a validation step showing how to verify the generated diagram matches the actual agent configuration (e.g., 'Run agent-test-delegation to validate accuracy').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy. The 'When to Use' and 'Use Cases' sections overlap significantly (both list documentation, onboarding, presentations). The 'Output Formats' section adds minimal value beyond what's already shown in the examples. | 2 / 3 |
Actionability | The skill provides concrete shell commands and example output formats, but the commands reference scripts (generate_hierarchy_diagram.sh, generate_mermaid_diagram.sh) without showing their contents or how to create them. If these scripts don't exist, the guidance is not executable. The examples are illustrative but not truly copy-paste ready for generating diagrams from actual agent configurations. | 2 / 3 |
Workflow Clarity | The skill shows individual commands but lacks a clear sequential workflow for generating and validating diagrams. There's no guidance on how to verify diagram accuracy against actual agent configuration, and the reference to 'agent-test-delegation' for validation is mentioned but not explained as a step in a process. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, appropriate length for a skill file, and references to external files for deeper information. The structure moves logically from quick reference to formats to use cases, with one-level-deep references at the end. | 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
d156cd1
- 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.