Content
10%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a persona dump, not a skill: it exhaustively enumerates Unity topics Claude already knows while providing zero concrete code, commands, workflows, or verification steps. Its only pointer to deeper material is a dangling reference to a file that is absent from the bundle.
Suggestions
Replace the Capabilities/Knowledge Base/Behavioral Traits lists with concrete, task-specific guidance: runnable C# snippets, profiler workflow commands, and specific optimization steps with expected measurements.
Create the referenced `resources/implementation-playbook.md` (and move the detailed capability material there) or remove the dangling reference — as written it points to a file that does not exist in the bundle.
Add a real workflow with validation checkpoints, e.g. profile baseline -> apply optimization -> re-profile to confirm the gain, with build/test verification steps before deployment.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~220-line body is almost entirely padded persona and capability enumerations ("Unity Profiler mastery for CPU, GPU, and memory analysis", "Observer pattern for decoupled system communication") that restate knowledge Claude already has about Unity, C#, and game architecture. | 1 / 5 |
Actionability | There is no code, command, or specific executable guidance anywhere; the body only describes what to provide ("Provide production-ready C# code with proper error handling") and its single reference points to a nonexistent file. | 1 / 5 |
Workflow Clarity | The Instructions section gives a rough generic sequence ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") but the steps are poorly defined, domain-agnostic filler with no validation checkpoints or concrete sequence for any real Unity task. | 2 / 5 |
Progressive Disclosure | Roughly 200 lines of capability, knowledge-base, and behavioral lists that belong in separate reference files are inlined, and the one reference ("If detailed examples are required, open `resources/implementation-playbook.md`") is buried in a bullet and does not exist in the bundle. | 2 / 5 |
Total | 6 / 20 Passed |