CtrlK
BlogDocsLog inGet started
Tessl Logo

033-architecture-diagrams

Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams, ER (Entity Relationship) diagrams, and bounded-context diagrams — through a modular, step-based interactive process that adapts to your specific visualization needs. This should trigger for requests such as Generate UML diagram; Create sequence diagram; Create class diagram; Create state machine diagram; Create deployment diagram; Create C4 diagram; Create bounded-context diagram; Create context-map diagram. Part of Plinth Toolkit

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured interactive skill with strong workflow sequencing, explicit validation feedback loops, and clean one-level-deep progressive disclosure. The main weakness is verbosity from duplicated content and repeated conditional clauses across the 12-question flow.

Suggestions

Remove or condense the "What is covered in this Skill?" section since it duplicates the frontmatter description and the question flow.

Factor the repeated "Ask this question only if you selected X in Question 1" preamble into a single stated rule rather than restating it under every question.

Consider collapsing the conditional gate text per question to a compact inline label to reduce token overhead.

DimensionReasoningScore

Conciseness

The body is mostly efficient but carries padding: the "What is covered in this Skill?" bullet list duplicates the description's diagram inventory, and each of the 12 questions repeats the conditional "Ask this question only if you selected ..." clause verbatim, which could be tightened.

3 / 5

Actionability

Provides concrete, executable commands ("./mvnw validate", "plantuml -checkonly diagrams", "plantuml -tpng diagrams", "plantuml -tsvg diagrams") and a precise question-to-reference mapping; the only gap is that PlantUML generation syntax itself lives in the references rather than inline, which is appropriate.

4 / 5

Workflow Clarity

A clear four-step sequence (validate → ask questions → read refs and generate → validate and finalize) with explicit validation checkpoints ("If validation fails, stop immediately") and a feedback loop requiring error resolution before proceeding.

5 / 5

Progressive Disclosure

The body is a well-organized overview that maps each selected diagram family to a single one-level-deep reference file; all seven referenced files in references/ exist and are clearly signaled in the closing Reference section.

5 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description that clearly states capabilities and provides explicit, natural trigger phrases for each diagram family. The only weakness is second-person voice ("Use when you need to generate") rather than third-person.

Suggestions

Rewrite in third-person voice (e.g., "Generates Java project diagrams ... Use when the user requests ...") to avoid the second-person penalty.

DimensionReasoningScore

Specificity

Lists multiple concrete diagram-generation actions across seven distinct diagram families ("generate UML sequence diagrams", "UML class diagrams", "C4 model diagrams", etc.) with comprehensive coverage, but the second-person phrasing "Use when you need to generate" triggers the voice penalty, reducing it from 5 to 4.

4 / 5

Completeness

Explicitly answers both what ("generate Java project diagrams ... through a modular, step-based interactive process") and when ("Use when you need to generate ..." plus concrete "This should trigger for requests such as" trigger phrases).

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases users would actually say ("Generate UML diagram; Create sequence diagram; Create class diagram; ... Create context-map diagram") including synonyms like Generate/Create and bounded-context/context-map.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Java project architecture diagrams via PlantUML) with distinct, specific triggers, giving minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/plinth
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.