Install any skill in seconds. Free to start, no credit card required.
Get Started Free →besty0728/unity-asmdef
Advises on Unity assembly definitions (asmdef) — module boundaries, dependency graphs, editor/runtime/test splits, and faster compile times.
Passed 22 of 22 test cases with the skill, and 19 of 22 without it.
3 fixed19 passed either way0 still failing0 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.
When starting a migration of an existing monolithic Unity project to assembly definitions, what should be isolated first to yield quick build safety wins?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends isolating Editor code from Runtime code as the first migration step | 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 when the project is large enough that compile boundaries and dependency direction matter.
asmdef is usually worth discussing when:
asmdef is justified nowMode: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).
test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.