graphviz-dot-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill graphviz-dot-generatorGraphviz Dot Generator - Auto-activating skill for Visual Content. Triggers on: graphviz dot generator, graphviz dot generator Part of the Visual Content skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just naming the skill without explaining its capabilities or providing useful trigger guidance. It relies entirely on users knowing the technical term 'Graphviz Dot' rather than describing the visual outputs it creates. The redundant trigger terms and lack of concrete actions make this description nearly useless for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates directed and undirected graphs, flowcharts, network diagrams, and hierarchical visualizations using DOT language syntax.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks for diagrams, flowcharts, graph visualizations, node-edge relationships, or mentions Graphviz, DOT files, or .gv files.'
Remove the redundant trigger term and add varied natural language terms users would actually say like 'diagram', 'flowchart', 'graph', 'visualization', 'network diagram'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Graphviz Dot Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating diagrams, generating graph visualizations, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' guidance is circular (use when user says 'graphviz dot generator'). No explicit trigger guidance for common use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('graphviz dot generator' listed twice) and overly technical. Missing natural user terms like 'diagram', 'flowchart', 'graph', 'visualization', 'nodes', 'edges', or '.dot files' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Graphviz Dot' is somewhat specific to this particular diagramming tool, but 'Visual Content' is generic and could overlap with other visualization skills. The lack of specific use cases increases conflict risk. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 information about DOT syntax, graph creation, or visualization workflows. The skill fails to teach Claude anything it doesn't already know.
Suggestions
Add concrete DOT syntax examples showing node definitions, edges, and common graph attributes (e.g., `digraph G { A -> B; B -> C; }`)
Include executable code for generating and rendering DOT files, such as using the `graphviz` Python library or command-line tools
Provide specific examples of common graph types (flowcharts, dependency graphs, state machines) with complete DOT code
Add a workflow section with steps: define graph structure, validate syntax, render to output format (PNG/SVG/PDF)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual Graphviz/DOT information. | 1 / 3 |
Actionability | Contains zero concrete guidance - no DOT syntax, no code examples, no actual commands. The entire skill describes what it could do rather than providing any executable instructions for generating Graphviz diagrams. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps for creating DOT files, no validation process, and no sequence of operations. The 'Capabilities' section lists abstract promises without any actual process. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples file, and no actual content worth organizing. It's not a monolithic wall of useful text - it's a wall of placeholder text. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.