Agent skill · software engineering · aiskillstore
allaymc-plugin-dev
Create, update and troubleshoot AllayMC plugins in Java or other JVM languages. Use when (1) creating a new AllayMC plugin. (2) migrating an existing plugin to AllayMC. (3) troubleshooting an AllayMC plugin.
Why this skill is useful
Provides specific commands and workflows for developing AllayMC plugins that the AI wouldn't reliably generate on its own.
What it needs
Requires gradle installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
AllayMC Plugin Development About AllayMC AllayMC is a third-party server software for Minecraft: Bedrock Edition written in Java. It provides a set of APIs for plugins to use. AllayMC is broadly divided into the following two modules: api: A set of interfaces provided for plugins. server: An implementation of the api. Plugins usually don't have access to it. About Plugin Plugins in AllayMC are just like Bukkit plugins, they are loaded by the server when the server starts. Plugins are used to extend server functionality. Workflow for a new plugin 1) Initialize the project Use the official template at references/JavaPluginTemplate If the user haven't initialize the project. If the user has already initialized the project, proceed to the next step. 2) Initialize Gradle and plugin metadata Before you begin, ask the user the following questions: What is the name of the plugin? What is the package name used by the plugin? What is the plugin author(s) name? What is the website of the plugin? What is the allay-api version used for the plugin? After the user answers the above questions, initialize the project metadata with the collected information. Before that, determine whether the user is using JavaPluginTemplate, which is implemented by determining whether the current project package name is org.allaymc.javaplugintemplate. Case 1: If the project is using JavaPluginTemplate: Rename package name from org.allaymc.javaplugintemplate to the user provided group name. Set the project name in settings.gradle.kts to the user provided plugin name. Update build.gradle.kts, solve all the TODOs inside. Case 2: If the project is not using JavaPluginTemplate: Update group, version (should start with 0.1.0), and description in build.gradle.kts. Keep package of the plugin main class aligned with the value of group in build.gradle.kts. Set the Java toolchain to 21 unless the user needs a different version in build.gradle.kts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/allaymc-plugin-dev