Skills allaymc-plugin-dev
📦

allaymc-plugin-dev

Content revision r1 Safe 📁 Filesystem access⚙️ External commands

Build AllayMC Plugins Faster

AllayMC plugin development requires correct metadata, Gradle setup, and lifecycle code. This skill guides Claude, Codex, and Claude Code through official references to create, update, and debug plugins.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "allaymc-plugin-dev" from https://skillstore.io/skills/allaymc-allaymc-plugin-dev.md and its manifest at https://skillstore.io/api/skills/allaymc-allaymc-plugin-dev/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "allaymc-plugin-dev". Create a new AllayMC plugin skeleton.

Expected outcome:

  • A short setup plan with required plugin name, package, author, website, and API version questions.
  • A project metadata update list for Gradle and plugin configuration.
  • A starter lifecycle class outline with load, enable, and disable responsibilities.

Using "allaymc-plugin-dev". My AllayMC plugin does not load on startup.

Expected outcome:

  • A checklist covering plugin entrance, package alignment, plugin metadata, and build output.
  • References to relevant Allay API or AllayGradle documentation paths.
  • A recommended verification step using the configured local server run command.

Security Audit

Safe
v11 • 7/9/2026 Open versioned report

The static findings are false positives caused by Markdown inline code, standard LGPL license text, and documented Gradle build commands. I found no prompt injection, data exfiltration intent, unsafe network behavior, or malicious command execution in the reviewed files.

4
Files scanned
664
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: claude View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/allaymc-allaymc-plugin-dev/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/allaymc-allaymc-plugin-dev/security.svg)](https://skillstore.io/skills/allaymc-allaymc-plugin-dev?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/allaymc-allaymc-plugin-dev?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/allaymc-allaymc-plugin-dev/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/allaymc-allaymc-plugin-dev.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

AllayMC. (2026). allaymc-plugin-dev security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/allaymc-allaymc-plugin-dev/audits/11

BibTeX citation

@techreport{allaymc-allaymc-allaymc-plugin-dev-2026, author = {AllayMC}, title = {allaymc-plugin-dev security audit report (audit version 11)}, institution = {Skillstore}, year = {2026}, number = {11}, url = {https://skillstore.io/skills/allaymc-allaymc-plugin-dev/audits/11}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "allaymc-plugin-dev security audit report (audit version 11)" version: "unspecified" type: report authors: - name: "AllayMC" date-released: "2026-07-09" url: "https://skillstore.io/skills/allaymc-allaymc-plugin-dev/audits/11" identifiers: - type: other value: "skillstore:allaymc-allaymc-plugin-dev:audit:11" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
71
Community
83
Spec Compliance

What You Can Build

Start a new plugin

Generate the initial project structure, package naming, metadata, and lifecycle entry class for an AllayMC plugin.

Migrate an existing plugin

Adapt an existing JVM plugin project to use AllayMC APIs, plugin metadata, and Gradle settings.

Troubleshoot build or runtime issues

Use AllayMC references to inspect API usage, Gradle configuration, and lifecycle behavior.

Try These Prompts

Create a basic plugin
Use allaymc-plugin-dev to create a new AllayMC plugin named ExamplePlugin with package com.example.plugin.
Configure plugin metadata
Use allaymc-plugin-dev to review my Gradle metadata, plugin entrance, authors, website, and target Allay API version.
Implement lifecycle behavior
Use allaymc-plugin-dev to add onLoad, onEnable, and onDisable behavior for my AllayMC plugin.
Diagnose a complex plugin issue
Use allaymc-plugin-dev to investigate this plugin error, compare my code with Allay API references, and propose a safe fix.

Best Practices

  • Clone submodules before asking for deep Allay API or template guidance.
  • Provide plugin name, package, author, website, and target API version at the start.
  • Run the generated plugin locally before publishing a jar.

Avoid

  • Do not rename packages or overwrite metadata without reviewing existing project structure.
  • Do not assume a plugin is reloadable unless the lifecycle code supports reload safely.
  • Do not rely on build success alone as proof that server runtime behavior works.

Frequently Asked Questions

What is this skill for?
It helps agents create, update, and troubleshoot AllayMC plugins using Java or other JVM languages.
Does it include official references?
Yes. The skill points to Allay docs, Allay source, AllayGradle, and a Java plugin template when submodules are present.
Can it build my plugin?
It can suggest Gradle build and run commands. The user or agent must run them in the project environment.
Can it migrate Bukkit plugins automatically?
It can guide migration work, but API differences and runtime behavior still require developer review and testing.
Which tools support this skill?
The report lists support for Claude, Codex, and Claude Code.
Is this skill safe to use?
The reviewed files show development guidance and documentation. The static security alerts were false positives in context.

Developer Details

Author

AllayMC

License

LGPL-2.1

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

1ffa7643651792ccb4bd3b15d924d2c97edff755

Maintenance freshness

7/18/2026

Usage

8 downloads · 273 views

File structure

📄 .gitmodules

📄 LICENSE

📄 README.md

📄 SKILL.md

View all