agent-hierarchy-diagram
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
82
Quality
76%
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 covers the core purpose and provides explicit usage triggers, which is a strength. However, it lacks comprehensive action verbs and natural keyword variations that users might employ. The trigger terms for when to use it ('documentation or onboarding') are too broad and could cause conflicts with other skills.
Suggestions
Add more natural trigger terms users might say, such as 'org chart', 'architecture diagram', 'agent structure', 'system hierarchy', or 'delegation flow'.
Make the 'Use when' clause more specific, e.g., 'Use when visualizing agent hierarchies, creating delegation flowcharts, or documenting multi-agent system structures'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (agent system diagrams) and one specific action (generate visual hierarchy diagrams showing levels and delegation), but lacks comprehensive actions like 'edit diagrams', 'export formats', or 'customize layouts'. | 2 / 3 |
Completeness | Clearly answers both what (generate visual hierarchy diagrams of agent system showing levels and delegation) and when (use for documentation or onboarding), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'visual hierarchy diagrams', 'agent system', 'documentation', 'onboarding', but misses common variations users might say like 'org chart', 'architecture diagram', 'system visualization', or 'agent structure'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to agent systems and hierarchy diagrams, but 'documentation' and 'onboarding' are generic triggers that could overlap with other documentation or diagramming skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that clearly explains how to generate hierarchy diagrams in multiple formats. The main weakness is that it references scripts that may not exist or aren't explained, creating a dependency gap. The content organization and token efficiency are excellent.
Suggestions
Either include the actual script content inline, or clarify that these scripts need to be created first with a pointer to where they should be located
Add a brief note about what to do if the scripts don't exist (e.g., manual creation steps or alternative approaches)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section serves a purpose - commands are direct, examples are minimal but complete, and there's no padding about what diagrams are or why visualization matters. | 3 / 3 |
Actionability | Provides concrete bash commands and example output formats, but the scripts referenced (generate_hierarchy_diagram.sh, generate_mermaid_diagram.sh) are not shown or explained. User cannot execute without those scripts existing, making this partially actionable. | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (generate diagrams). The workflow is clear: run script, get output, save to location. No multi-step validation needed for read-only diagram generation. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Quick Reference, formats, use cases). References to related files are one level deep and clearly signaled. Content is appropriately sized for a SKILL.md overview. | 3 / 3 |
Total | 11 / 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
6213d1a
- 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.