113-java-maven-documentation
Use when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from the project pom.xml, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects. Part of the skills-for-java project
89
86%
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 purpose, includes explicit trigger guidance with 'Use when', and provides specific technical context about Maven projects. The description is distinctive and uses natural terminology that Java/Maven developers would recognize and use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create a DEVELOPER.md file', 'combining a fixed base template with dynamic sections', 'Plugin Goals Reference', 'Maven Profiles table', and 'Submodules table for multi-module projects'. | 3 / 3 |
Completeness | Explicitly answers both what (create DEVELOPER.md with dynamic sections from pom.xml) and when ('Use when you need to create a DEVELOPER.md file for a Maven project'). The 'Use when' clause is present at the start. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'DEVELOPER.md', 'Maven project', 'pom.xml', 'Plugin Goals', 'Maven Profiles', 'Submodules', 'multi-module projects'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Maven projects + DEVELOPER.md generation + pom.xml parsing. Unlikely to conflict with other skills due to the specific combination of Maven, DEVELOPER.md, and the particular sections mentioned. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates good conciseness and progressive disclosure, appropriately deferring detailed content to a reference file. However, it sacrifices actionability by providing no concrete examples of output format or template structure in the main skill, and references workflow steps (1-5) that aren't visible without reading the external file.
Suggestions
Add a brief example showing the expected DEVELOPER.md output structure or a sample Plugin Goals table format
Include at least a summary of the 5 steps referenced, even if details are in the reference file
Add a concrete example of a valid plugin declaration vs an inherited one to clarify the plugin scope constraint
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding unnecessary explanations. It assumes Claude understands Maven concepts and focuses only on what's needed for the task. | 3 / 3 |
Actionability | The skill provides clear constraints and scope but lacks concrete examples of the output format, template structure, or executable commands. All actual guidance is deferred to the reference file. | 2 / 3 |
Workflow Clarity | References 'steps 1-5' but doesn't define them inline - they're in the reference file. The mandatory read-first constraint is clear, but the actual workflow sequence is not visible in the skill itself. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview, constraints, and a single well-signaled reference to detailed guidance. The reference is one level deep and clearly indicated. | 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
7772a1b
- 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.