114-java-maven-search
Covers Maven Central search (Search API, maven-metadata.xml, artifact URLs) and project-local update reports via versions-maven-plugin (display-property-updates, display-dependency-updates, display-plugin-updates). Use when finding or verifying coordinates, browsing Central, or checking what newer versions apply to the user’s pom.xml. This should trigger for requests such as Search Maven Central; Find Maven dependency; Maven coordinates; groupId artifactId version. Part of cursor-rules-java project
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/114-java-maven-search/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 its scope around Maven Central search and dependency version management. It provides specific actions, explicit trigger guidance with natural user phrases, and occupies a distinct niche. The description is well-structured and comprehensive without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: Maven Central search (Search API, maven-metadata.xml, artifact URLs), project-local update reports via versions-maven-plugin with specific goals (display-property-updates, display-dependency-updates, display-plugin-updates), finding/verifying coordinates, and checking newer versions against pom.xml. | 3 / 3 |
Completeness | Clearly answers both 'what' (Maven Central search, artifact URL construction, versions-maven-plugin update reports) and 'when' with explicit trigger guidance ('Use when finding or verifying coordinates, browsing Central, or checking what newer versions apply') plus example trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'Search Maven Central', 'Find Maven dependency', 'Maven coordinates', 'groupId artifactId version', 'pom.xml', 'newer versions'. These cover common variations of how users would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Maven Central search and Maven dependency version checking. The specific mentions of Maven Central, versions-maven-plugin, pom.xml, and groupId/artifactId/version make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like an index or overview document than an actionable skill. It correctly identifies the scope and points to a reference file, but provides no concrete examples, executable commands, API query templates, or URL patterns in the body itself. The workflow steps are too abstract to guide Claude without reading the reference first, and there are no validation/feedback loops for operations that depend on external API responses.
Suggestions
Add at least one concrete, executable example of a Maven Central Search API query (e.g., a curl command or fetch URL with expected JSON response structure) directly in the skill body.
Include a concrete URL pattern example for maven-metadata.xml and artifact downloads (e.g., `https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-starter-parent/maven-metadata.xml`).
Add a validation checkpoint in the workflow — e.g., 'Verify the Search API returns results before asserting coordinates; if 0 results, try alternate query syntax or report to user.'
Trim the 'When to use this skill' keyword list and the redundant introductory paragraph to reduce token usage without losing information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy — the introductory paragraph largely restates the bullet list that follows, and the 'When to use this skill' section is essentially a keyword list that adds little actionable value. Some tightening is possible. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete API query examples, no URL templates, and no sample commands beyond naming goals like `versions:display-property-updates`. All real guidance is deferred to the reference file, making this skill essentially a table of contents rather than actionable instruction. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence, but they are abstract ('Perform Maven Central discovery and verification') rather than concrete. There are no validation checkpoints — e.g., no explicit step to verify a 200 response from the Search API before proceeding, and no error-recovery feedback loop for failed coordinate lookups. | 2 / 3 |
Progressive Disclosure | There is a single clear reference to a detailed file, which is good. However, the SKILL.md itself contains almost no standalone actionable content — it over-delegates to the reference, meaning a reader gets very little value without following the link. The balance between overview and reference is off. | 2 / 3 |
Total | 7 / 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
899d988
- 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.