CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

minecraft-bukkit-pro

Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/minecraft-bukkit-pro/SKILL.md

The canonical home for this skill is minecraft-bukkit-pro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

25%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a persona statement plus a catalog of topic areas with essentially no executable guidance — no code, commands, or validation steps — padded with generic engineering advice. Its one progressive-disclosure pointer is broken, so detailed material neither exists nor is reachable.

Suggestions

Fix or remove the broken "open resources/implementation-playbook.md" reference — no such file or directory exists in the bundle; if detailed examples are intended, create them under references/ and link them from a clearly signaled "Advanced" section.

Replace the topic catalogs with a concrete quick start: a minimal plugin.yml, a build.gradle/Maven dependency snippet (paper-api), and one compilable event-listener example.

Cut the tautological "Use this skill when / Do not use this skill when" sections and generic platitudes (SOLID, Google Java Style, README advice), and add a sequenced workflow with validation checkpoints (compile → unit-test with MockBukkit → deploy to a test server → verify in game).

DimensionReasoningScore

Conciseness

The body contains several padded sections that add nothing Claude doesn't know: tautological triggers ("Working on minecraft bukkit pro tasks or workflows"), generic Instructions ("Apply relevant best practices and validate outcomes"), and software-engineering platitudes ("Design with SOLID principles", "Follow Google Java Style Guide", "Comprehensive README with quick start"). This matches anchor 2 (noticeably verbose, several unnecessary/padded sections) rather than 3, where excess would be limited to a few spots.

2 / 5

Actionability

Across ~115 lines there is no code, command, config snippet, or executable step — only topic lists ("Event-driven architecture with listener priorities", "Async operations for I/O") and a handful of named tools (MockBukkit, Spark, HikariCP). The single concrete pointer — "open resources/implementation-playbook.md" — targets a file that does not exist in the bundle. That fits anchor 2 (high-level hints, missing specific steps); not 1 because some concrete tool names are given.

2 / 5

Workflow Clarity

"Project Analysis" → "Implementation Strategy" → "Quality Standards" is a rough ordering of concerns, not a sequenced workflow; there are no validation checkpoints or feedback loops (e.g., compile → test with MockBukkit → load on a test server → verify). This matches anchor 2 (rough sequence, poorly defined steps, validation absent).

2 / 5

Progressive Disclosure

The only reference is buried in a bullet inside "Instructions" ("open resources/implementation-playbook.md") and is dangling — no resources/, references/, scripts/, or assets/ directory exists in the bundle. Meanwhile ~90 lines of expertise catalog that belong in reference files are inlined in SKILL.md. This matches anchor 2 (content that belongs in separate files is inlined; references buried/broken).

2 / 5

Total

8

/

20

Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies a distinctive niche and includes the natural trigger terms users would say, but it only communicates "what" at a high level and omits any "when to use" guidance. Adding concrete capabilities and an explicit Use-when clause would move it toward the top anchors.

Suggestions

Add an explicit trigger clause, e.g., "Use when developing, debugging, or optimizing plugins for Minecraft servers, or when the user mentions Bukkit, Spigot, Paper, or plugin.yml/Java plugin projects."

Enumerate concrete actions instead of the single verb "Master", e.g., "Build, debug, and optimize Minecraft server plugins: event listeners, Brigadier commands, inventory GUIs, NBT data, and async database access."

Include natural phrasing variants users actually type ("Bukkit plugin", "Spigot plugin", "Paper plugin", "plugin.yml") to round out trigger coverage.

DimensionReasoningScore

Specificity

"Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs" names the domain and one concrete capability (plugin development) plus the three named APIs, but does not list multiple concrete actions (e.g., building event listeners, commands, or GUIs). It matches anchor 3 (domain + 1-2 concrete actions), not 4 (no several-action list) and not 2 (more than minimal — the specific APIs are named).

3 / 5

Completeness

The "what" is clear (plugin development for Bukkit/Spigot/Paper), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 2 because the "what" is clear rather than vague; not 4 because "when" is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

"Minecraft", "server plugin", "Bukkit", "Spigot", and "Paper" are natural terms users would actually say when needing this skill. A few natural phrasings and synonyms (e.g., "Spigot plugin", ".jar") are missing, so it fits anchor 4 rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Bukkit/Spigot/Paper plugin development is a clear niche with highly distinctive trigger words, but the words "Minecraft server" create minor overlap risk with non-plugin tasks (server administration, configuration). Fits anchor 4 (mostly distinct, minor overlap with closely related domains) rather than 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/minecraft-bukkit-pro/SKILL.md

Revision

64adc55

Reviewed

Table of Contents

DiscoveryImplementationValidation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill