AC mcsmanager-controller
Control and troubleshoot MCSManager-managed Minecraft servers through the MCSManager API and clearly provided host-side context. Use when asked to start, stop, restart, inspect, or debug an MCSManager instance; read or tail server logs; send console commands; or check instance status. Use only with configuration the user explicitly provides in the task context or in a local config file the user has intentionally set up for this skill.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 45 steps, 1 vague phrases
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 879 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 438: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 45 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.