111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), or architecture testing (ArchUnit) — and want a consultative, question-driven approach that adds only what you actually need. Part of the skills-for-java project
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is a strong skill description that clearly defines its scope, lists specific tools and capabilities, and includes an explicit 'Use when' trigger clause. The named libraries and frameworks serve as excellent trigger terms that are both natural and distinctive. The only minor note is the trailing 'Part of the skills-for-java project' which adds context but doesn't contribute to skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: adding/evaluating Maven dependencies, nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit). Also mentions the consultative, question-driven approach. | 3 / 3 |
Completeness | Explicitly answers both 'what' (add or evaluate Maven dependencies for code quality across specific categories) and 'when' (opens with 'Use when you need to add or evaluate Maven dependencies that improve code quality'). The 'Use when' clause is present and detailed. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Maven dependencies', 'code quality', 'nullness annotations', 'JSpecify', 'static analysis', 'Error Prone', 'NullAway', 'VAVR', 'ArchUnit', 'functional programming', 'architecture testing'. These cover both general concepts and specific tool names. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Maven code-quality dependencies with specific named tools (JSpecify, Error Prone, NullAway, VAVR, ArchUnit). Very unlikely to conflict with other skills due to the narrow, well-defined scope and explicit tool names. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured interactive skill with clear workflow sequencing, proper validation checkpoints, and good progressive disclosure to a reference file. Its main weakness is that the skill body itself lacks any concrete executable content (no Maven dependency XML snippets, no example question wording), making it heavily dependent on the reference file for actionability. The coverage list and 'when to use' section have notable overlap that could be tightened.
Suggestions
Include at least one concrete example dependency snippet (e.g., the JSpecify dependency XML) directly in the skill body so Claude has immediate actionable content without needing to read the reference file.
Consolidate the 'What is covered' and 'When to use this skill' sections to eliminate redundancy — one section listing the four dependency categories with trigger phrases would suffice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — the bullet list under 'What is covered' and the 'When to use this skill' section overlap significantly. The parenthetical descriptions in the coverage list add minor clutter. | 2 / 3 |
Actionability | Provides concrete validation commands (`./mvnw validate`, `mvn validate`) and a clear sequence constraint, but all actual implementation details (dependency snippets, exact question wording, configuration) are deferred to the reference file. The skill itself contains no executable code or copy-paste-ready dependency blocks. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced: validate first, stop on failure, then ask questions in strict order (JSpecify → Enhanced Compiler Analysis → VAVR → ArchUnit), add only selected items. Explicit validation checkpoint with a feedback loop (stop and fix before proceeding) is present for the destructive/modification operation. | 3 / 3 |
Progressive Disclosure | Clean overview structure with a single, clearly signaled one-level-deep reference to the detailed guidance file. The SKILL.md serves as a concise entry point without inlining the full reference content. | 3 / 3 |
Total | 10 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
9ec21dd
- 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.