114-java-maven-search
This Claude Code skill enables searching Maven Central Repository, resolving artifact coordinates (groupId:artifactId:version), reading version history, and constructing download URLs for JARs and documentation. It also helps users verify dependency and plugin updates in their own Maven projects via the versions-maven-plugin, providing structured coordinate output and verifiable HTTPS repository links. Use this skill when locating dependencies, confirming artifact availability, checking for newer versions, or building correct Maven Central URLs.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/114-java-maven-search && cp -r /tmp/114-java-maven-search/skills/114-java-maven-search ~/.claude/skills/114-java-maven-searchSKILL.md
# Maven Central search and coordinates Help users search Maven Central, resolve **groupId:artifactId:version**, read version history, and build correct download URLs; and when working on **their** project, verify `versions-maven-plugin` and run `versions:display-*` goals for dependency, plugin, and property updates. **What is covered:** - Maven Central Search API — e.g. keyword search for Spring Boot starters (`spring-boot-starter`) or coordinate filters (`g:org.springframework.boot AND a:spring-boot-starter-parent`) - Direct repository layout and `maven-metadata.xml` - POM, JAR, `-sources.jar`, `-javadoc.jar` URL patterns - Parsing POMs for direct dependencies; transitive trees via Maven/Gradle on the consumer project - Versions Maven Plugin — ensure `org.codehaus.mojo:versions-maven-plugin` is declared, then `./mvnw versions:display-property-updates`, `versions:display-dependency-updates`, `versions:display-plugin-updates` - Output format: structured coordinates, tables, and verifiable HTTPS links ## Constraints Verify coordinates against the Search API or repository responses before asserting availability. Prefer release versions unless snapshots are explicitly required. - **VERIFY**: Do not invent GAVs — confirm via Search API or successful GET of metadata/POM - **FORMAT**: Always express full coordinates as `groupId:artifactId:version` when a version is fixed - **BEFORE APPLYING**: Read the reference for step-by-step workflows, query syntax, and URL patterns - **EDGE CASE**: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands - **EDGE CASE**: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance - **EDGE CASE**: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off ## When to use this skill - Search Maven Central - Find Maven dependency - Maven coordinates - groupId artifactId version - Latest version Maven - maven-metadata.xml - Download JAR from Maven Central - Download javadocs - Dependency tree transitive - display-dependency-updates - display-plugin-updates - Outdated Maven dependencies ## Workflow 1. **Read Maven search reference workflow** Read `references/114-java-maven-search.md` before forming queries, coordinate checks, or URL outputs. 2. **Perform Maven Central discovery and verification** Use Search API and repository metadata/POM checks to confirm valid coordinates and available versions. 3. **Format results with full coordinates and links** Return `groupId:artifactId:version` outputs, structured tables, and verifiable HTTPS artifact URLs. 4. **Run project-local update checks when applicable** When working on a local project, ensure versions-maven-plugin usage and run `versions:display-*` reports for properties, dependencies, and plugins. ## Reference For detailed guidance, examples, and constraints, see [references/114-java-maven-search.md](references/114-java-maven-search.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project