graphviz-dot-generator
Graphviz Dot Generator - Auto-activating skill for Visual Content. Triggers on: graphviz dot generator, graphviz dot generator Part of the Visual Content skill category.
35
3%
Does it follow best practices?
Impact
94%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/graphviz-dot-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak — it is essentially just a skill name repeated with boilerplate category metadata. It provides no concrete actions, no natural trigger terms users would say, and no explicit guidance on when Claude should activate this skill. It would be nearly indistinguishable from other visual/diagramming skills in a multi-skill environment.
Suggestions
Add concrete capability descriptions such as 'Generates Graphviz DOT language code to create directed graphs, flowcharts, network diagrams, and dependency trees'.
Include a 'Use when...' clause with natural trigger terms like 'diagram', 'flowchart', 'graph visualization', 'DOT syntax', 'node-edge diagram', 'dependency graph', or 'Graphviz'.
Remove the duplicated trigger term and replace with diverse, natural user phrases that cover common variations of how users request graph/diagram generation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Graphviz Dot Generator') but does not describe any concrete actions like 'creates diagrams', 'generates graph layouts', or 'converts data to DOT syntax'. It is essentially a title repeated with no capability details. | 1 / 3 |
Completeness | There is no explanation of what the skill does beyond its name, and no explicit 'Use when...' clause or equivalent guidance on when Claude should select this skill. Both 'what' and 'when' are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'graphviz dot generator' repeated twice. It misses natural user phrases like 'diagram', 'flowchart', 'graph', 'DOT language', 'node and edge diagram', 'visualization', or 'directed graph'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Graphviz' and 'Dot' does narrow the domain to a specific tool, which provides some distinctiveness. However, the vague 'Visual Content' category and lack of concrete triggers could cause overlap with other diagramming or visualization skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content about Graphviz DOT generation. It contains only generic boilerplate text that could apply to any skill topic, with zero actionable guidance, no code examples, no DOT syntax, and no real information. It provides no value beyond what Claude already knows.
Suggestions
Add concrete, executable DOT syntax examples (e.g., a complete digraph with nodes, edges, and attributes that Claude can use as a template).
Include specific guidance on common graph types (flowcharts, dependency graphs, state machines) with copy-paste-ready DOT code for each.
Define a clear workflow: gather requirements → choose graph type → generate DOT code → validate syntax → render output, with validation steps.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content about Graphviz features, styling options, and layout engines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'graphviz dot generator' excessively, and provides zero actual technical content about generating Graphviz DOT diagrams. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no DOT syntax examples, no executable code, no commands, no specific instructions on how to generate or structure Graphviz diagrams. Every bullet is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.