CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-hierarchy-diagram

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

78

1.39x
Quality

65%

Does it follow best practices?

Impact

85%

1.39x

Average score across 6 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

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

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.

A compact, well-structured skill body that respects token budget and shows concrete usage, but its core executable guidance is undermined by references to script files that are absent from the bundle and an advertised GraphML output with no way to produce it. Fixing the dangling script references would move this from adequate to solid.

Suggestions

Ship the referenced scripts (./scripts/generate_hierarchy_diagram.sh and ./scripts/generate_mermaid_diagram.sh) in the bundle, or remove the Quick Reference commands that invoke them.

Provide the command or script for the GraphML output format advertised in Output Formats, or drop the format from the list.

Merge the redundant "When to Use" and "Use Cases" sections, and add a one-line validation step (e.g. cross-check the diagram against .claude/agents/ config) to tighten the workflow.

DimensionReasoningScore

Conciseness

The body is lean — terse sections, minimal prose, no explanations of concepts Claude already knows — fitting 'efficient; minor instances of over-explanation that could be trimmed'. The main trimmable redundancy is the overlap between "When to Use" and "Use Cases", which repeat the documentation/onboarding rationale, keeping it below 5.

4 / 5

Actionability

The Quick Reference gives concrete copy-paste commands ("./scripts/generate_hierarchy_diagram.sh", "./scripts/generate_mermaid_diagram.sh > hierarchy.mmd"), but no scripts/ directory or script files exist in the bundle, so the primary commands are not actually executable. Additionally, GraphML is advertised in Output Formats with no command to produce it — concrete guidance that is incomplete, matching the 3 anchor rather than 'mostly executable with minor gaps'.

3 / 5

Workflow Clarity

As a simple single-purpose skill (run a script, redirect output), the action is unambiguous and the Quick Reference shows three concrete invocations, warranting a high score under the simple-skill note. It is not 5 because one of the three advertised output formats (GraphML) has no generation path, leaving a gap in the workflow, and there is no step for verifying the generated diagram matches the actual agent configuration.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections (When to Use, Quick Reference, format examples, Output Formats, References) with small inline examples appropriately sized for the overview, and references like "/agents/hierarchy.md" and ".claude/agents/" are one level deep and clearly labeled — 'good structure; most content appropriately placed; references mostly clear'. It is not 5 because the key pointers to ./scripts/*.sh lead to files that do not exist in the bundle, a 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.

A serviceable description with a clear 'what' and an explicit 'use for' clause, but it stops short of comprehensive: no output formats, no synonyms, and 'when' guidance states purpose rather than natural user triggers. It sits squarely between the mediocre bad-examples and the polished good-examples.

Suggestions

Add concrete trigger phrases: e.g. "Use when the user asks to visualize the agent hierarchy, document delegation chains, or prepare onboarding materials."

Mention the concrete deliverables in the description (ASCII tree, Mermaid, GraphML outputs) to sharpen specificity and distinctiveness.

Include natural synonyms users would say, such as "org chart", "agent structure", or "team layout", to improve trigger term coverage.

DimensionReasoningScore

Specificity

"Generate visual hierarchy diagrams of agent system showing levels and delegation" names the domain and a concrete action with what the diagrams show, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It does not list the output formats (ASCII, Mermaid, GraphML) or multiple distinct actions that would warrant a 4.

3 / 5

Completeness

The 'what' is clear ("Generate visual hierarchy diagrams of agent system showing levels and delegation") and the 'when' is explicitly stated ("Use for documentation or onboarding"), so the missing-trigger cap of 3 does not apply. However, the 'when' describes purpose rather than concrete user trigger phrases, so it falls short of the 5 anchor.

4 / 5

Trigger Term Quality

Keywords present are "hierarchy diagrams", "levels", "delegation", "documentation", "onboarding" — some relevant terms users might say, but common variations like "org chart", "agent structure", "visualize the team", or "who reports to whom" are missing, fitting the 'some relevant keywords but missing common variations or synonyms' anchor rather than the sparse 2 or well-covered 4.

3 / 5

Distinctiveness Conflict Risk

"agent system" + "hierarchy diagrams" + "delegation" carves a clear niche that would rarely collide with unrelated skills, fitting 'mostly distinct; minor overlap risk'. It is not a 5 because it could still overlap with generic diagramming or documentation-visualization skills given no sharper trigger phrasing.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
majiayu000/claude-skill-registry
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.