SKILLEMALL.ai

BD mc-server-plugin-security

我的世界(Minecraft)服务器插件安全经验库。记录已验证有效的加固做法(经验)和踩过的安全坑(漏洞原理+判定+解法),全部脱敏。涉及 AuthMe 登录插件、Bukkit/Spigot/Paper/Leaf/Folia/Arclight/NeoForge 插件安全、登录绕过、session 劫持、ForceOp、插件消息伪造、权限漏洞、0day 排查、jar 静态检查、插件版本比对与升级时使用;搭建或维护 MC 服务器前先查看,避免重蹈覆辙。触发词:AuthMe、登录插件、MC 插件安全、ForceOp、session 劫持、插件 0day、绕登录、Bukkit、Paper、Leaf、插件升级、jar 检查。

ClawHub Agent Skills v0.1.5 4 files body ≈ 3 870 tokens Open the sourceclawhub.ai analyzed 2 d ago

我的世界(Minecraft)服务器插件安全经验库。记录已验证有效的加固做法(经验)和踩过的安全坑(漏洞原理+判定+解法),全部脱敏。涉及 AuthMe 登录插件、Bukkit/Spigot/Paper/Leaf/Folia/Arclight/NeoForge 插件安全、登录绕过、session…

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "created"
  • note frontmatter-key unknown frontmatter key "updated"

Process rating: all ten parameters 45/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 20 mutating operations with no state check
  • 60Tools and files. Uses tools (web, git) that frontmatter does not declare
  • 100Steps. 82 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3870 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (8 tags): a typed call is more reliable

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +2Single-language instructions
  • +3Description length 311: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 82 items
  • +4Has examples (1 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
The skill is a Minecraft plugin security reference, but it tells the agent to persistently rewrite the skill from future conversations without clear user approval or maintainer review.
LLM: suspicious (high)