maven-central-publisher

Automates publishing Java, Kotlin, or JVM libraries to Maven Central via Portal API or central-publishing-maven-plugin.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-old --skill maven-central-publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maven-central-publisher
Source: https://github.com/trancee/MeshLink-old/tree/main/.agents/skills/maven-central-publisher
Command: npx skills add https://github.com/trancee/MeshLink-old --skill maven-central-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Maven Central publishing for Java, Kotlin, or JVM libraries is error-prone and manually intensive; this skill automates the entire process—from preparing POM metadata and GPG signing to uploading bundles via the Central Publisher Portal and tracking validation.

Core Features & Use Cases

  • End-to-end publishing: generate Maven-compatible artifacts (jar, sources, javadoc), sign them, and upload a bundle through the Portal.
  • migration and CI: support OSSRH migration to the Central Portal, Gradle or Maven workflows, and GitHub Actions-based automation.
  • Use case: release a new library to Maven Central directly from CI, with automatic validation and optional auto-publish.

Quick Start

Configure your project for central publishing with either the central-publishing-maven-plugin (Maven) or a zero-dependency Gradle/Portal API flow, then trigger a publish workflow from your CI.

Frequently Asked Questions about maven-central-publisher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a JVM library to Maven Central via the Central Publisher Portal?

To publish a JVM library to Maven Central, generate Maven-compatible artifacts, sign them with GPG, and upload a bundle through the Central Publisher Portal for validation. This skill supports end-to-end automation using Maven or Gradle workflows.

Can I migrate from OSSRH to the Central Publisher Portal for Maven Central publishing?

Yes, you can migrate from OSSRH to the Central Publisher Portal for Maven Central publishing. This skill handles the migration process, transitioning your existing workflows to the new portal for artifact uploading, signature verification, and validation tracking.

Does this approach support Gradle and GitHub Actions for Maven Central publishing?

Yes, Maven Central publishing supports Gradle and GitHub Actions integration. This skill enables you to trigger a release workflow directly from your CI, using a zero-dependency custom Portal API integration for bundle packaging, checksums, and status polling.

Why does my Maven Central publishing fail with 401 or credential issues?

Maven Central publishing fails with 401 or credential issues due to incorrect portal authentication configuration. This skill troubleshoots common errors like 401s, missing POM elements, and credential misconfigurations to ensure successful bundle validation and upload.

What do I need to prepare for GPG signing and POM metadata when publishing to Maven Central?

For GPG signing and POM metadata when publishing to Maven Central, you need to configure your project to generate required artifacts like sources and javadoc. This skill automates the preparation of POM metadata and signatures to meet portal validation requirements.