agent-hierarchy-diagram

Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.

1.39x

Quality

65%

Does it follow best practices?

Impact

85%

1.39x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/agent/agent-hierarchy-diagram/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and lean with usable diagram templates, but its main executable commands depend on scripts that are missing from the bundle, weakening actionability. It is a competent single-purpose skill with one concrete defect.

Suggestions

Either ship the referenced ./scripts/generate_hierarchy_diagram.sh and generate_mermaid_diagram.sh in a scripts/ bundle, or replace the bash commands with the inline ASCII/Mermaid templates Claude can produce directly.

Add a brief validation step (e.g. cross-check generated levels against .claude/agents/ or run agent-test-delegation) so the diagram's accuracy can be confirmed.

Collapse the overlapping 'When to Use' and 'Use Cases' sections into one to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, though the 'When to Use' and 'Use Cases' sections partially overlap and could be merged.	4 / 5
Actionability	Provides concrete bash commands and ready-to-use ASCII/Mermaid templates, but the primary commands reference ./scripts/generate_hierarchy_diagram.sh and ./scripts/generate_mermaid_diagram.sh that are not present in any bundle directory.	3 / 5
Workflow Clarity	As a simple single-purpose generation skill the action is unambiguous via the Quick Reference block, though no validation step confirms the produced diagram matches the real agent tree.	4 / 5
Progressive Disclosure	Well-organized sections with one-level-deep references and a clear References list, but the body points at ./scripts/* bundle files that do not exist, leaving a minor navigation gap.	4 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 cleanly states a capability and provides explicit trigger guidance, but the trigger contexts are generic and the action list is thin. It is solid but not exemplary.

Suggestions

Broaden the 'when' clause with concrete natural triggers, e.g. 'Use when visualizing agent structure, delegation chains, or onboarding new contributors to the agent system'.

Add a second concrete action (e.g. 'export as ASCII, Mermaid, or GraphML') to lift specificity beyond a single verb.

Include synonyms a user would naturally say ('agent structure', 'team hierarchy') to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Generate visual hierarchy diagrams") with two depicted aspects ("levels and delegation"), but offers only a single action rather than a list of specific operations.	3 / 5
Completeness	Explicitly states both what ("Generate visual hierarchy diagrams of agent system showing levels and delegation") and when ("Use for documentation or onboarding"), though the trigger clause is somewhat terse and could be more specific.	4 / 5
Trigger Term Quality	Includes relevant terms ("hierarchy diagrams", "documentation", "onboarding", "delegation") but misses common natural variations like "agent structure", "team chart", or "visualize agents".	3 / 5
Distinctiveness Conflict Risk	The agent-hierarchy-diagram niche is mostly distinct, but the "documentation or onboarding" triggers are broad enough to overlap with other doc-generation skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: majiayu000/claude-skill-registry
Path: skills/agent/agent-hierarchy-diagram/SKILL.md
Commit: 04324c6

Reviewed: about 22 hours ago

Table of Contents

Discovery Implementation Validation

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.