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 essentially an auto-generated stub that repeats the skill name without providing any meaningful information about capabilities, use cases, or trigger scenarios. It lacks concrete actions, natural trigger terms, and explicit 'when to use' guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions such as 'Generates PlantUML diagrams including sequence diagrams, class diagrams, activity diagrams, and component diagrams from text-based descriptions.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks for UML diagrams, sequence diagrams, class diagrams, flowcharts, or mentions PlantUML, .puml files, or diagram generation from code.'
Remove the duplicate trigger term and replace with diverse natural language variations users would actually say, such as 'UML', 'diagram', 'flowchart', 'sequence diagram', 'architecture diagram'.
| 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 title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant repetition of the skill name rather than explicit trigger guidance. 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', 'diagram from code', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'PlantUML' does provide some specificity that distinguishes it from generic diagramming skills, but the lack of detail about what types of diagrams or use cases it covers means it could overlap with other visual/diagram 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 PlantUML diagram generation. It contains only generic boilerplate text that repeats the skill name without providing any syntax, examples, commands, or actionable guidance. It fails on every dimension of the rubric.
Suggestions
Add concrete PlantUML syntax examples for common diagram types (sequence, class, activity, component) with copy-paste ready @startuml/@enduml blocks.
Include a quick-start workflow: write .puml file → render with specific command (e.g., `java -jar plantuml.jar diagram.puml`) → verify output.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching PlantUML usage.
Add references to separate files for advanced diagram types or styling options if the skill needs to cover multiple diagram categories.
| 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 actual technical content about PlantUML syntax, commands, or usage. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no PlantUML syntax examples, no executable code, no specific commands, no diagram templates. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, no validation checkpoints. The phrase 'step-by-step guidance' is mentioned but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed files, no structured sections with real content, and no navigation to additional resources. | 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
b8a3b3e
- 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.