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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill plantuml-diagram-generator

What are skills?

1.85x

Quality

Does it follow best practices?

Impact

100%

1.85x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/plantuml-diagram-generator/SKILL.md

SKILL.md

Review

Evals

Discovery

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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger guidance. It lacks concrete actions, natural user keywords, and explicit 'when to use' instructions. The duplicate trigger term suggests auto-generated content that wasn't properly reviewed.

Suggestions

Add specific actions the skill performs, e.g., 'Creates UML diagrams including sequence diagrams, class diagrams, activity diagrams, and flowcharts using PlantUML syntax'

Include a 'Use when...' clause with natural trigger terms like 'UML', 'sequence diagram', 'class diagram', 'flowchart', 'architecture diagram', '.puml files'

Remove the duplicate trigger term and expand with variations users would naturally say when needing diagram generation

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 PlantUML syntax).	1 / 3
Completeness	The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a duplicate trigger phrase. There is no explicit 'Use when...' clause or meaningful trigger guidance.	1 / 3
Trigger Term Quality	The trigger terms are just 'plantuml diagram generator' repeated twice, which is redundant and misses natural variations users might say like 'UML diagram', 'sequence diagram', 'class diagram', 'flowchart', or '.puml'.	1 / 3
Distinctiveness Conflict Risk	The mention of 'PlantUML' specifically does provide 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

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 that provides no actual value for PlantUML diagram generation. It contains only generic boilerplate describing what a skill should do without any PlantUML-specific syntax, examples, diagram types, or actionable guidance. The content would need to be completely rewritten with actual PlantUML content.

Suggestions

Add executable PlantUML code examples showing basic diagram syntax (e.g., sequence diagrams, class diagrams, activity diagrams)

Include the PlantUML syntax reference or link to detailed syntax documentation for different diagram types

Provide a quick-start section with a minimal working example that can be copy-pasted

Remove all generic boilerplate text ('provides automated assistance', 'follows industry best practices') and replace with specific PlantUML guidance

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing specific about PlantUML. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands implicitly.	1 / 3
Actionability	No concrete code, commands, or PlantUML syntax examples are provided. The skill describes what it does abstractly ('provides step-by-step guidance') rather than actually providing any executable guidance or PlantUML diagram examples.	1 / 3
Workflow Clarity	No workflow, steps, or process is defined. The content only describes when the skill activates and what it claims to do, without any actual sequence of actions for creating PlantUML diagrams.	1 / 3
Progressive Disclosure	The content is a flat, generic template with no meaningful structure. There are no references to detailed documentation, examples, or syntax guides that would help with PlantUML diagram creation.	1 / 3
	Total	4 / 12 Passed

Validation

81%

Warnings & errors only

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

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.