AC openplanet-plugin-dev
Create, debug, structure, and run Openplanet AngelScript plugins for Trackmania 2020 (TMNEXT) and ManiaPlanet 4 (TM2/MP4). Covers API quirks, AngelScript pitfalls, performance patterns, the launch/verify loop, MP4 API-mismatch fixes, and proven templates. Use when building, debugging, reviewing, or launching Openplanet plugins.
Create, debug, structure, and run Openplanet AngelScript plugins for Trackmania 2020 (TMNEXT) and ManiaPlanet 4 (TM2/MP4).
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: 29. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 59, 62, 193): check that old rules are not kept next to new ones — the full check reads the text for contradictions
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 (bash, python) that frontmatter does not declare
- 70Execution cost. Instruction body is 4031 tokens
- 100Steps. 25 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 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
- +1No license
- +2Single-language instructions
- +3Description length 329: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (23 of 24)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.