Java Maven
Spin up a consistent Java 21 Maven project layout with validation, logging, and Spring Boot–style POM defaults for agent-assisted JVM apps.
Overview
java-maven is an agent skill for the Build phase that supplies Maven project configuration, example POM wiring, and schema-backed settings for Java backend scaffolding.
Install
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-java --skill java-mavenWhat is this skill?
- YAML skill config with dev/production validation strictness and log-level overrides
- Example pom.xml with Java 21 compiler source/target and Spring Boot starter-web dependency
- JSON Schema draft-07 stub for validating java-maven configuration shape
- Integration toggles for git, linter, and formatter in generated settings
- Markdown output format with optional examples in validation output
- Example POM targets Java 21 with maven.compiler.source and target
- Sample dependency uses spring-boot-starter-web version 3.2.0
Adoption & trust: 663 installs on skills.sh; 37 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want to start a Java Maven service quickly but your agent keeps improvising incompatible POM fragments and inconsistent project settings.
Who is it for?
Solo builders bootstrapping a Java 21 Maven jar or Spring-style web backend with agent help and a single config source of truth.
Skip if: Teams that already maintain a mature parent POM, multi-module reactor, or need Gradle-only workflows without Maven.
When should I use this skill?
You need Maven project defaults, POM structure, or java-maven YAML settings for a new or agent-guided JVM backend.
What do I get? / Deliverables
You get a aligned skill config, sample pom.xml, and validation defaults your agent can extend into a buildable Maven tree.
- Skill YAML configuration block
- Starter pom.xml fragment
- JSON Schema configuration outline
Recommended Skills
Journey fit
Maven scaffolding and POM structure are core build-phase work before you ship a JVM service or library. Backend is the canonical shelf because the skill centers on project packaging, compiler targets, and dependency wiring—not frontend or ops runbooks.
How it compares
Use as a Maven scaffold template skill, not as a substitute for DevOps CI/CD or container deploy skills.
Common Questions / FAQ
Who is java-maven for?
Solo and indie builders shipping JVM backends who want agents to follow a fixed Maven and YAML configuration pattern instead of one-off POM snippets.
When should I use java-maven?
Use it in the Build phase when creating a new Java Maven project, tuning compiler levels, or aligning agent output with Spring Boot–style dependencies before you write application code.
Is java-maven safe to install?
Treat it like any third-party agent skill: review the Security Audits panel on this Prism page and inspect generated POM and config before you run mvn or commit secrets.
SKILL.md
READMESKILL.md - Java Maven
# java-maven Configuration # Category: general # Generated: 2025-12-30 skill: name: java-maven version: "1.0.0" category: general settings: # Default settings for java-maven enabled: true log_level: info # Category-specific defaults validation: strict_mode: false auto_fix: false output: format: markdown include_examples: true # Environment-specific overrides environments: development: log_level: debug validation: strict_mode: false production: log_level: warn validation: strict_mode: true # Integration settings integrations: # Enable/disable integrations git: true linter: true formatter: true <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0"> <modelVersion>4.0.0</modelVersion> <groupId>com.example</groupId> <artifactId>myapp</artifactId> <version>1.0.0</version> <packaging>jar</packaging> <properties> <java.version>21</java.version> <maven.compiler.source>${java.version}</maven.compiler.source> <maven.compiler.target>${java.version}</maven.compiler.target> </properties> <dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> <version>3.2.0</version> </dependency> </dependencies> </project> { "$schema": "http://json-schema.org/draft-07/schema#", "title": "java-maven Configuration Schema", "type": "object", "properties": { "skill": { "type": "object", "properties": { "name": { "type": "string" }, "version": { "type": "string", "pattern": "^\\d+\\.\\d+\\.\\d+$" }, "category": { "type": "string", "enum": [ "api", "testing", "devops", "security", "database", "frontend", "algorithms", "machine-learning", "cloud", "containers", "general" ] } }, "required": [ "name", "version" ] }, "settings": { "type": "object", "properties": { "enabled": { "type": "boolean", "default": true }, "log_level": { "type": "string", "enum": [ "debug", "info", "warn", "error" ] } } } }, "required": [ "skill" ] } # Java Maven Guide ## Overview This guide provides comprehensive documentation for the **java-maven** skill in the custom-plugin-java plugin. ## Category: General ## Quick Start ### Prerequisites - Familiarity with general concepts - Development environment set up - Plugin installed and configured ### Basic Usage ```bash # Invoke the skill claude "java-maven - [your task description]" # Example claude "java-maven - analyze the current implementation" ``` ## Core Concepts ### Key Principles 1. **Consistency** - Follow established patterns 2. **Clarity** - Write readable, maintainable code 3. **Quality** - Validate before deployment ### Best Practices - Always validate input data - Handle edge cases explicitly - Document your decisions - Write tests for critical paths ## Common Tasks ### Task 1: Basic Implementation ```python # Example implementation pattern def implement_java_maven(input_data): """ Implement java-maven functionality. Args: input_data: Input to process Returns: Processed result """ # Validate input if not input_data: raise ValueError("Input required") # Process result = process(input_data) # Return return result ``` ### Task 2: Advanced Usage For advanced scenarios, consider: - Configuration customization via `assets/config.yaml` - Validation using `scripts/validate.py` - Integration with other skills ## Troubleshooting ### Common Issues