plantuml-diagram-generator
Plantuml Diagram Generator - Auto-activating skill for Visual Content. Triggers on: plantuml diagram generator, plantuml diagram generator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.85xAverage 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/plantuml-diagram-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 an auto-generated label with a duplicated trigger term and no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms users would use, and lacks any explicit guidance on when Claude should select it.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates PlantUML diagrams including sequence diagrams, class diagrams, activity diagrams, and component diagrams from textual descriptions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for UML diagrams, PlantUML code, sequence diagrams, class diagrams, flowcharts, or .puml files.'
Remove the duplicated trigger term and expand with varied natural keywords users would actually say, such as 'UML', 'diagram', 'flowchart', 'sequence diagram', 'class diagram', 'PlantUML syntax'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Plantuml Diagram Generator') but does not describe any concrete actions like 'generates sequence diagrams, class diagrams, activity diagrams from text descriptions.' It is essentially just a label repeated. | 1 / 3 |
Completeness | The description barely answers 'what does this do' (generates PlantUML diagrams, implied only from the name) and has no explicit 'when should Claude use it' clause. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('plantuml diagram generator, plantuml diagram generator'). It misses natural user terms like 'UML', 'sequence diagram', 'class diagram', 'flowchart', '.puml', 'PlantUML syntax', or 'generate diagram'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'PlantUML' does provide some specificity that distinguishes it from generic diagram or visualization skills, but the vague 'Visual Content' category and lack of concrete scope 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/placeholder with no actual content about PlantUML diagram generation. It contains no syntax examples, no diagram type guidance, no executable code, and no actionable instructions whatsoever. Every section is generic boilerplate that could apply to any skill topic by swapping the name.
Suggestions
Add concrete PlantUML syntax examples for common diagram types (sequence, class, activity, component) with copy-paste ready @startuml/@enduml blocks.
Include a clear workflow: define diagram type → write PlantUML markup → validate syntax → render output, with specific validation steps.
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content like a PlantUML syntax quick reference and common patterns.
Add references to PlantUML-specific features like themes, includes, and styling options, either inline or via well-signaled supporting files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'plantuml diagram generator' excessively, and contains zero substantive information about actually generating PlantUML diagrams. | 1 / 3 |
Actionability | There are no concrete instructions, no PlantUML syntax examples, no executable code, no commands, and no specific guidance. The skill describes what it could do rather than providing any actionable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, no validation checkpoints—just vague claims like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful organization of content across sections. | 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
3a2d27d
- 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.