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
59
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 excels in specificity by naming concrete tools and APIs, provides natural trigger terms users would actually use, and includes explicit 'Use when' guidance. The description is well-structured, distinctive, and would allow Claude to confidently select this skill from a large pool.
| 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 triggers ('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 functions primarily as a table of contents pointing to a reference file, with almost no actionable content in the body itself. The constraints and edge cases are well-articulated, but the complete absence of concrete examples, executable commands, API query syntax, or URL templates means Claude would be unable to act on this skill without the reference file. The workflow steps are too abstract to guide real execution.
Suggestions
Add at least one concrete Search API query example (e.g., `curl 'https://search.maven.org/solrsearch/select?q=g:org.springframework.boot+AND+a:spring-boot-starter-parent&rows=5&wt=json'`) and a sample response snippet to make the skill actionable without requiring the reference file.
Include a concrete URL pattern template for repository layout, e.g., `https://repo1.maven.org/maven2/{groupId-with-slashes}/{artifactId}/{version}/{artifactId}-{version}.pom`.
Add a validation checkpoint in the workflow, e.g., 'Verify the coordinate exists by checking HTTP 200 on the POM URL before returning results to the user.'
Remove or significantly trim the 'When to use this skill' keyword list — this is metadata that belongs in frontmatter, not body content, and wastes tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary enumeration of what's covered (the bullet list in the intro largely restates things Claude would understand from context), and the 'When to use this skill' section is essentially keyword stuffing. However, the constraints and workflow sections are reasonably tight. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands (beyond naming Maven goals), no API query examples, no URL templates, and no sample outputs. The skill describes what to do abstractly ('Use Search API and repository metadata/POM checks') but never shows how. All real content is deferred to the reference file. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence, but they are vague ('Perform Maven Central discovery and verification') with no validation checkpoints. There's no feedback loop for when coordinate verification fails or when versions-maven-plugin is missing. The workflow reads more like a high-level outline than actionable steps. | 2 / 3 |
Progressive Disclosure | The skill references a single detailed file (references/114-java-maven-search.md) which is good one-level-deep structure, but since no bundle files were provided we can't verify the reference exists or is well-structured. The SKILL.md itself is somewhat monolithic in its intro section while simultaneously being too thin on actual content — it's an awkward middle ground where too much is deferred and what remains isn't well-organized. | 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
3b97275
- 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.