plantuml-diagram-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill plantuml-diagram-generatorPlantuml Diagram Generator - Auto-activating skill for Visual Content. Triggers on: plantuml diagram generator, plantuml diagram 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 restating the skill name without providing any meaningful information about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The only slight positive is the specific mention of PlantUML technology.
Suggestions
Add specific capabilities like 'Creates UML diagrams including sequence diagrams, class diagrams, activity diagrams, and flowcharts from text descriptions or code analysis'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks for UML diagrams, sequence diagrams, class diagrams, PlantUML code, or wants to visualize code architecture'
Add file type triggers and common variations: '.puml files, PlantUML, UML, diagram from code, visualize relationships'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Plantuml Diagram Generator' without describing any concrete actions. It doesn't explain what the skill actually does (e.g., creates sequence diagrams, class diagrams, generates code from descriptions). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There's no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The triggers listed are just 'plantuml diagram generator' repeated twice. Missing natural variations users would say like 'UML diagram', 'sequence diagram', 'class diagram', 'flowchart', or 'PlantUML code'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'PlantUML' specifically provides some distinctiveness from generic diagram tools, but '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
0%This skill is essentially an empty template that describes what a PlantUML skill should do without providing any actual PlantUML guidance. It contains no syntax examples, no diagram types, no code snippets, and no actionable instructions. The entire content is self-referential boilerplate that would provide zero value to Claude when generating PlantUML diagrams.
Suggestions
Add concrete PlantUML syntax examples for common diagram types (sequence, class, activity, component) with executable @startuml/@enduml blocks
Include a quick-start section with a minimal working example that can be copy-pasted and rendered
Define a clear workflow: 1) Identify diagram type needed, 2) Generate PlantUML code, 3) Validate syntax, 4) Suggest rendering options
Replace the meta-description sections with actual PlantUML reference content covering syntax, styling options, and common patterns
| 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 PlantUML-specific information. | 1 / 3 |
Actionability | Contains zero executable guidance - no PlantUML syntax, no code examples, no actual diagram generation instructions. The entire content describes what the skill supposedly does rather than providing any concrete instructions on how to create PlantUML diagrams. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Claims to provide 'step-by-step guidance' but contains no actual steps. There are no sequences, no validation checkpoints, and no process for creating or validating PlantUML diagrams. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual content to organize. There are no references to detailed materials, no examples files, and no structured navigation to additional resources. | 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.