SKILLEMALL.ai
GitHub ↗ RU Sign in

AC minecraft-plugin-development

Use this skill when building or modifying Minecraft server plugins for Paper, Spigot, or Bukkit, including plugin.yml setup, commands, listeners, schedulers, player state, team or arena systems, persistent progression, economy or profile data, configuration files, Adventure text, and version-safe API usage. Trigger for requests like "build a Minecraft plugin", "add a Paper command", "fix a Bukkit listener", "create plugin.yml", "implement a minigame mechanic", "add a perk or quest system", or "debug server plugin behavior".

github/awesome-copilot Agent Skills author: github MIT 9 files body ≈ 3 040 tokens Open the sourcegithub.com↗ analyzed 21 h ago

yml setup, commands, listeners, schedulers, player state, team or arena systems, persistent progression, economy or profile data, configuration files…

As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, progress reporting

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: GitHub Copilot / VS Code Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
96
Run on models
none yet
Process rating
C
61/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
50
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 195): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 61/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 117 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3040 tokens
    • 100Running it twice. Mutating operations check current state
    • low 10 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 7 example trigger phrases
    • +3Description length 529: enough signal without eating the budget
    • +4Structure: 22 headings
    • +3Step-by-step instructions: 117 items
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (8 of 8)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.