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
69
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/113-java-maven-documentation/SKILL.mdQuality
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 what the skill does (generates DEVELOPER.md files from Maven project pom.xml with specific dynamic sections) and when to use it (when creating DEVELOPER.md for Maven projects). It includes excellent domain-specific trigger terms and is highly distinctive. The only minor note is the trailing 'Part of the skills-for-java project' which adds context but doesn't contribute to selection criteria.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating a DEVELOPER.md file, combining a fixed base template with dynamic sections, deriving content from pom.xml, generating Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects. | 3 / 3 |
Completeness | Clearly answers both 'what' (create a DEVELOPER.md file combining a base template with dynamic sections from pom.xml) and 'when' (explicitly starts with 'Use when you need to create a DEVELOPER.md file for a Maven project'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'DEVELOPER.md', 'Maven project', 'pom.xml', 'Plugin Goals Reference', 'Maven Profiles', 'Submodules', 'multi-module projects'. These are terms a developer working with Maven would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of DEVELOPER.md generation, Maven pom.xml parsing, and specific output sections (Plugin Goals Reference, Maven Profiles table, Submodules table) creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill acts primarily as a thin wrapper pointing to a reference file, with almost no actionable content in the body itself. The workflow steps (1-5) are referenced but never defined, and there are no concrete examples, templates, or executable commands. While the constraints and scope are reasonably stated, the skill cannot stand on its own without the reference file.
Suggestions
Include at least a summary of the 5 steps in the skill body so Claude understands the workflow without needing to read the reference file first.
Add a concrete example of the expected output format (e.g., a sample Plugin Goals Reference table or Profiles table) so the skill is actionable on its own.
Provide the base template inline or at minimum show its structure, since it's described as 'verbatim' reproduction — Claude needs to see it to reproduce it.
Remove the 'When to use this skill' keyword list, as this is trigger/routing metadata that doesn't belong in the instructional body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered in this Skill?' section and the 'When to use this skill' keyword list add some unnecessary bulk. The constraints section partially repeats itself (the introductory sentence before the bullet list restates the first two bullets). However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, templates, or executable examples. It describes what to do at a high level ('read every pom.xml', 'execute steps 1-5') but the actual steps, base template, plugin catalog, and detailed constraints are all deferred entirely to the reference file. Claude cannot act on this skill alone. | 1 / 3 |
Workflow Clarity | The skill mentions 'execute steps 1–5 in order' but never defines what those steps are. The actual workflow is entirely absent from the skill body and fully delegated to the reference file, making the sequence unclear and unverifiable from this content alone. | 1 / 3 |
Progressive Disclosure | There is a clear reference to a single external file for detailed guidance, which is good structure. However, the skill body itself contains too little actionable content — it's essentially just a pointer to the reference file with some constraints, making the split feel like the skill is hollow rather than a useful overview. | 2 / 3 |
Total | 6 / 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.