agent-hierarchy-diagram
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
Install with Tessl CLI
npx tessl i github:majiayu000/claude-skill-registry-data --skill agent-hierarchy-diagram80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 both what the skill does and when to use it, earning full marks for completeness. However, it lacks specificity in listing multiple concrete actions and could benefit from more natural trigger terms that users would actually say. The distinctiveness is moderate due to generic use case triggers.
Suggestions
Add more specific actions like 'edit existing diagrams', 'export to PNG/SVG', or 'customize node styling' to improve specificity
Include natural trigger term variations such as 'org chart', 'architecture diagram', 'agent structure', 'system hierarchy', or 'delegation tree'
| 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 natural 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 many other skills. Could conflict with general diagramming or documentation 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 without showing their implementation or explaining how to customize diagram generation. The skill assumes the scripts exist and work correctly.
Suggestions
Show the core logic of the diagram generation scripts or provide inline code for generating diagrams without external scripts
Add guidance on how to customize diagrams (e.g., filtering to specific subtrees, changing styling)
| 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. The examples show output format but not how to create custom diagrams or modify the scripts. | 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 | |
- 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.