CtrlK
BlogDocsLog inGet started
Tessl Logo

node-link-and-diagram-layout

Choose and apply automatic layout strategies for node-link diagrams and connected-node visuals. Use when the user asks how to auto-arrange nodes, reduce line crossings, route edges, avoid overlaps, stabilize layout, or choose graph-layout algorithms for network diagrams, dependency graphs, database schema diagrams, ERDs, state machines, decision trees, flow diagrams, box-and-line editors, or other line-connected nodes.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 well-organized, instruction-oriented skill that excels at structure and progressive disclosure with real reference files. Its weakness is actionability: it gives a strong decision framework and stack names but no executable code or commands to apply them.

Suggestions

Add a short, concrete runnable example for at least one common case (e.g. a Graphviz dot snippet or an ELK config snippet) so the guidance is executable, not just descriptive.

Tighten the long enumerated lists (graph families, reading tasks, stack defaults) by moving the exhaustive catalogs into the references and keeping only the high-signal entries inline.

Make the final validation step an explicit validate-and-iterate loop (e.g. 'if crossings/overlaps exceed threshold, adjust routing family and re-run') to strengthen the workflow feedback pattern.

DimensionReasoningScore

Conciseness

Mostly lean and avoids explaining concepts Claude already knows, but the long enumerated lists (graph families, reading tasks, stack defaults) are somewhat dense and could be trimmed or pushed to references.

4 / 5

Actionability

Provides a thorough decision framework and named stack defaults (Graphviz dot/neato, ELK, React Flow), but offers no executable code or commands — guidance is instructional rather than copy-paste ready.

3 / 5

Workflow Clarity

The Core Workflow is a clearly numbered 8-step sequence with a final validation step against readability criteria, though validation is framed as criteria-checks rather than an explicit re-run/feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep references (algorithm-selection.md, layered-tree-force-and-radial-layouts.md, routing-overlap-and-quality.md) that all exist in the bundle, plus clear navigation in the Reference Guide.

5 / 5

Total

16

/

20

Passed

Description

96%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 strong, well-structured description with concrete capabilities and explicit 'Use when' trigger guidance covering many natural phrasings. Minor distinctiveness overlap with sibling visualization skills keeps it just short of a perfect conflict-risk score.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'auto-arrange nodes, reduce line crossings, route edges, avoid overlaps, stabilize layout' — with comprehensive coverage across distinct layout tasks.

5 / 5

Completeness

Explicitly answers both what ('Choose and apply automatic layout strategies for node-link diagrams') and when ('Use when the user asks how to auto-arrange nodes...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-phrase coverage including user-facing terms like 'auto-arrange nodes', 'reduce line crossings', and a long synonym/notation list (dependency graphs, ERDs, state machines, decision trees, flow diagrams).

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (layout algorithm selection for node-link diagrams) but overlaps slightly with adjacent data-visualization and UML skills given the shared diagram vocabulary.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.