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.
38
Quality
7%
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 essentially a placeholder that names the skill but provides no substantive information about its capabilities or when to use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The duplicate trigger term suggests auto-generated content that wasn't reviewed.
Suggestions
Add specific actions the skill performs, e.g., 'Creates directed and undirected graphs, flowcharts, network diagrams, and hierarchical visualizations using DOT syntax'
Include a 'Use when...' clause with natural trigger terms like 'diagram', 'flowchart', 'graph visualization', 'node relationships', 'DOT file', or 'network graph'
Remove the duplicate trigger term and expand to include variations users would naturally say when requesting graph visualizations
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Graphviz Dot Generator') without describing any concrete actions. It lacks verbs describing what the skill actually does (e.g., 'creates diagrams', 'generates flowcharts', 'visualizes relationships'). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section is not a proper 'Use when...' clause and contains duplicate terms. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('graphviz dot generator' repeated twice) and miss natural user language like 'diagram', 'flowchart', 'graph', 'visualize', 'DOT language', or 'node graph'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Graphviz' is a specific tool name that provides some distinctiveness, the vague 'Visual Content' category and lack of specific use cases could cause overlap with other diagramming or visualization skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic template with no actual Graphviz DOT content. It lacks any executable examples, DOT syntax guidance, or concrete instructions for generating diagrams. The entire body could be replaced with actual DOT code examples and syntax patterns.
Suggestions
Add executable DOT code examples showing basic graph syntax (e.g., `digraph G { A -> B -> C; }`)
Include specific node/edge attribute examples (shapes, colors, labels, styles)
Provide a concrete workflow: write DOT -> validate syntax -> render to PNG/SVG
Remove generic boilerplate sections ('Purpose', 'Capabilities', 'Example Triggers') and replace with actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Graphviz DOT syntax. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, DOT syntax examples, or executable commands are provided. The skill describes what it does abstractly but never shows how to actually generate Graphviz diagrams. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. Claims to provide 'step-by-step guidance' but includes zero actual steps for creating DOT graphs. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, but there are no references to detailed materials, examples, or external documentation. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 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
0c08951
- 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.