AB rngneeds-unity
Teach agents how to design, implement, explain, and debug gameplay randomness with the RNGNeeds Unity plugin. Use when a request involves RNGNeeds types or concepts such as ProbabilityList, ProbabilityItem, PLCollection, weighted picks, loot tables, gacha, spawn tables, dialogue weighting, AI choice weighting, repeat prevention, depletable lists, card deck extensions, deck order, draw pile, discard pile, hand, graveyard, shuffle plans, influence providers, pick history, seeding, or custom selection methods in Unity/C#.
As a process B 69/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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: 10. 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 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 85Steps. 34 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 986 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 524: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 34 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.