111-java-maven-dependencies

Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a consultative, question-driven approach that adds only what you actually need. This should trigger for requests such as Add Maven dependencies; Add JSpecify nullness dependencies; Add Error Prone NullAway dependencies; Add VAVR functional dependencies; Add ArchUnit architecture testing dependencies; Add JavaMoney dependencies. Part of Plinth Toolkit

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/111-java-maven-dependencies/SKILL.md

Quality

Content

71%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.

The body is well-structured with a clear validated workflow and excellent progressive disclosure into four real reference files. Its main weakness is redundancy between the body's trigger/coverage lists and the frontmatter description, which hurts conciseness.

Suggestions

Remove the 'When to use this skill' section (it duplicates the description's triggers) or replace it with a one-line pointer, trimming the most obvious padding.

Fold the 'What is covered in this Skill?' list into the workflow's reference-mapping step so each family is named once.

Make the validation feedback loop explicit on the Claude side ('re-run mvn validate after the user reports a fix') to push workflow clarity to 5.

Dimension	Reasoning	Score
Conciseness	The 'When to use this skill' and 'What is covered in this Skill?' sections duplicate the dependency-family and trigger lists already present in the description, adding padding that could be trimmed without losing information.	3 / 5
Actionability	Provides concrete commands ('./mvnw validate' or 'mvn validate'), exact reference paths, and a dot-notation example; minor gaps are the absence of any dependency XML inline, which is justified by progressive disclosure.	4 / 5
Workflow Clarity	A clear four-step sequence with an explicit validation checkpoint and a stop-on-failure feedback gate; the re-validation loop is delegated to the user ('ask the user to fix issues') rather than an explicit Claude-side fix-and-retry cycle.	4 / 5
Progressive Disclosure	The body is an overview that splits per-family detail into four real one-level-deep reference files (all verified to exist), clearly signaled in both the workflow's reference-mapping list and the closing Reference section.	5 / 5
	Total	16 / 20 Passed

Description

78%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.

The description is comprehensive and trigger-rich, clearly stating both purpose and invocation conditions with concrete library-specific triggers. Its main weaknesses are limited action-verb variety and second-person voice, which costs it on specificity.

Suggestions

Rewrite in third person ('Use when adding or evaluating Maven dependencies...') to recover the specificity point lost to second-person voice.

Broaden action verbs beyond 'add/evaluate' (e.g., 'configure', 'audit', 'remove') to better reflect the consultative workflow described in the body.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (add/evaluate Maven dependencies) across five named families (JSpecify, Error Prone + NullAway, VAVR, ArchUnit, JavaMoney), but the action verbs are limited to add/evaluate; reduced by 1 for second-person voice ('Use when you need...', 'you actually need') per the rubric guideline.	3 / 5
Completeness	Explicitly answers both what (add/evaluate Maven dependencies for code quality and domain modeling, with named families) and when via a clear 'Use when...' clause plus 'This should trigger for requests such as...' with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger phrases a user would say ('Add Maven dependencies', 'Add JSpecify nullness dependencies', 'Add ArchUnit architecture testing dependencies'), though a few natural variations (e.g. 'pom.xml', 'dependency management') are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct niche (specific code-quality Maven libraries) with minimal conflict risk, though it has minor overlap with a generic Maven-dependency addition skill.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/111-java-maven-dependencies/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.