Content
22%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a hollow shell — it has a title, scope markers, and a reference to an external file, but contains zero actionable Unity DOTS/ECS content in the body itself. The instructions are generic boilerplate that could apply to any skill and provide no domain-specific guidance. Without the referenced bundle file, this skill teaches Claude nothing about ECS patterns, Job System usage, or Burst Compiler optimization.
Suggestions
Add at least 2-3 concrete, executable ECS code examples in the SKILL.md body (e.g., defining an IComponentData struct, writing an ISystem, scheduling a job with Burst) so the skill provides immediate actionable value.
Replace the generic boilerplate instructions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') with specific Unity DOTS workflow steps, such as: define components → create systems → schedule jobs → validate with Entity Debugger.
Include the `resources/implementation-playbook.md` bundle file or inline its key patterns so the skill actually contains teachable content rather than deferring everything to a missing file.
Remove the 'Do not use this skill when' section (it's trivially obvious) and use that space for a quick-reference table of common ECS patterns or a decision tree for when to use IJobEntity vs SystemAPI.Query.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Do not use this skill when' section is trivially obvious and wastes tokens. The 'Use this skill when' section is reasonable but somewhat generic. The Instructions section is entirely boilerplate ('Clarify goals, constraints, and required inputs') that adds no domain-specific value. | 3 / 5 |
Actionability | There is zero concrete guidance — no code examples, no specific commands, no ECS patterns, no component definitions, no system implementations. The instructions are entirely vague platitudes like 'Apply relevant best practices and validate outcomes' with no Unity DOTS-specific content whatsoever. | 1 / 5 |
Workflow Clarity | There is no workflow defined. The four bullet points in Instructions are generic meta-instructions with no sequencing, no validation steps, and no domain-specific process. There is nothing that guides Claude through any ECS-related task. | 1 / 5 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable one-level-deep reference. However, no bundle files were provided to verify the reference exists, and the SKILL.md itself contains essentially no substantive overview content to serve as a useful entry point — it's almost entirely empty of real information, making the reference feel like a deflection rather than progressive disclosure. | 3 / 5 |
Total | 8 / 20 Passed |