allaymc-plugin-dev

Automate AllayMC plugin creation, migration, and debugging workflows.

1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/AllayMC/AllaySkill --skill allaymc-plugin-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: allaymc-plugin-dev
Source: https://github.com/AllayMC/AllaySkill/tree/main
Command: npx skills add https://github.com/AllayMC/AllaySkill --skill allaymc-plugin-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AllayMC plugin development often involves repetitive setup, template wiring, and manual configuration that slows delivery. This Skill provides a repeatable workflow to scaffold, migrate, and troubleshoot AllayMC plugins across JVM languages.

Core Features & Use Cases

  • Initialize a project from official templates (JavaPluginTemplate and AllayPluginTemplate) and manage submodules
  • Configure Gradle, plugin metadata, and plugin.json as needed for AllayGradle or non-AllayGradle setups
  • Implement the plugin entry and core logic; build and test locally with Gradle tasks (runServer, shadowJar)

Quick Start

Create a new AllayMC plugin project by following the template-guided setup and run it locally to verify plugin startup.

Frequently Asked Questions about allaymc-plugin-dev

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

FAQPage Schema
How do I scaffold an AllayMC plugin from a template?

Scaffolding an AllayMC plugin initializes a project from official templates like JavaPluginTemplate, configures Gradle and plugin.json metadata, and sets up the plugin entry point to eliminate repetitive manual wiring.

How do I configure Gradle for an AllayMC plugin project?

Configuring Gradle for AllayMC plugins involves setting up build metadata for AllayGradle or non-AllayGradle setups. The workflow manages plugin.json requirements and Gradle tasks like shadowJar to package your build correctly.

Can I use JVM languages other than Java for AllayMC plugin development?

Yes, AllayMC plugin development supports Java-based JVM languages. The workflow handles project initialization, migration, and debugging across these languages while enforcing Gradle and YAML frontmatter requirements.

What is the best way to run and test an AllayMC plugin locally?

Testing an AllayMC plugin locally uses Gradle tasks like runServer and shadowJar. This builds the project and starts a local server instance to verify plugin startup and core logic implementation.

How do I migrate an existing plugin to a new AllayMC template?

Migrating an AllayMC plugin updates template wiring, reconfigures Gradle and plugin.json metadata, and adjusts the plugin entry. The workflow automates troubleshooting and enforces YAML frontmatter requirements during migration.

What are the YAML frontmatter requirements for AllayMC plugins?

YAML frontmatter requirements for AllayMC plugins enforce specific metadata formatting during project initialization and migration. The workflow validates these fields and supports optional references, scripts, and assets.