agent-hierarchy-diagram

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

1.39x

Quality

—

Does it follow best practices?

Impact

85%

1.39x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is concrete and actionable with copy-paste commands and clear examples for a simple single-task skill, but it carries mild section redundancy and references script bundle files that are not actually bundled.

Suggestions

Merge the redundant "When to Use" and "Use Cases" sections into one consolidated list to remove overlapping content and tighten token usage.

Either include the referenced ./scripts/generate_hierarchy_diagram.sh and generate_mermaid_diagram.sh in a scripts/ bundle or replace the commands with self-contained inline examples so all referenced paths resolve to real files.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and example-driven with no concept-explanation padding, but the "When to Use" and "Use Cases" sections cover overlapping ground (documenting/onboarding/presentations), which 'could be tightened' into a single section.	2 / 3
Actionability	The Quick Reference gives concrete, copy-paste-ready commands ("./scripts/generate_hierarchy_diagram.sh", "./scripts/generate_mermaid_diagram.sh > hierarchy.mmd") plus concrete ASCII and Mermaid examples, matching 'fully executable commands; specific examples; copy-paste ready'.	3 / 3
Workflow Clarity	This is a simple single-action skill (run a script to emit a diagram) with an unambiguous command sequence in Quick Reference; per the simple-skills note, a clear single-action workflow with no destructive/batch step needing validation scores 3.	3 / 3
Progressive Disclosure	The SKILL.md is well-sectioned and references are one level deep, but the Quick Reference and References point to ./scripts/*.sh bundle files that are not present in the bundle, so navigation does not resolve to real files — 'references present but not clearly signaling actual content'.	2 / 3
	Total	10 / 12 Passed

Description

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 clearly states what the skill does and includes an explicit use-trigger, but its trigger coverage is thin and the "documentation or onboarding" framing is generic enough to risk overlap with other doc skills.

Suggestions

Broaden trigger terms to natural phrases users would say (e.g., "agent org chart", "diagram agent structure", "delegation tree", "visualize agent hierarchy") to improve trigger_term_quality.

List the concrete output formats as actions in the description (e.g., "Generate ASCII, Mermaid, and GraphML hierarchy diagrams") to raise specificity beyond a single composite action.

Sharpen the "when" clause beyond generic "documentation or onboarding" to agent-structure-specific contexts (e.g., "Use when onboarding contributors to the agent system or documenting delegation chains") to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	It names one concrete action ("Generate visual hierarchy diagrams") plus two attributes ("showing levels and delegation"), but does not list multiple distinct concrete actions like the score-3 example, so it sits at 'names domain and some actions, not comprehensive'.	2 / 3
Completeness	It states both what ("Generate visual hierarchy diagrams of agent system showing levels and delegation") and when via an explicit "Use for documentation or onboarding" trigger clause, satisfying the 'explicit trigger guidance' requirement that prevents a cap at 2.	3 / 3
Trigger Term Quality	The trigger clause offers only "documentation or onboarding" — relevant but thin, missing common variations a user would naturally say (e.g., "agent org chart", "diagram the agent structure", "visualize delegation"), fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	"agent hierarchy diagrams" is a fairly distinct niche, but the generic "documentation or onboarding" triggers could overlap with other documentation/onboarding skills, matching 'somewhat specific but could still overlap with similar skills'.	2 / 3
	Total	9 / 12 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
Commit: cb3ef45

Reviewed: about 19 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.