Install any skill in seconds. Free to start, no credit card required.
Get Started Free →besty0728/unity-script-roles
Advises on assigning Unity script roles — whether a class should be a MonoBehaviour, ScriptableObject, plain C# service, or installer.
Passed 21 of 22 test cases with the skill, and 19 of 22 without it.
3 fixed18 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a script to sit on a 3D spatial GameObject and trigger Unity AudioSource component methods when requested by my core sound service. What is the appropriate role?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends a MonoBehaviour bridge role to interface directly with Unity AudioSource components | Passed | Passed |
| Explains that direct engine component interaction requires MonoBehaviour | Missed | Passed |
The instructions your model reads when the skill loads.
Before calling any skill in this module: if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via
GET /skills/recommend?includeSchema=true) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.
Use this skill before creating a batch of gameplay scripts.
Turn a rough script list into explicit roles so AI does not generate everything as MonoBehaviour.
MonoBehaviour bridgeScriptableObject config/dataMode: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).
MonoBehaviour.ScriptableObject onto runtime state that should stay in memory-only objects.test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.