unity-ecs-patterns
Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/game-development/skills/unity-ecs-patterns/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and completeness, featuring an explicit 'Use when' clause and highly distinctive technology-specific terminology. Its main weakness is that the capabilities described are somewhat high-level ('building data-oriented games, optimizing performance') rather than listing specific concrete actions the skill enables. The word 'Master' at the beginning is slightly informal/imperative rather than third-person descriptive.
Suggestions
Replace the imperative 'Master' with third-person phrasing like 'Guides development with Unity ECS...' or 'Provides patterns and code for Unity ECS...'
Add specific concrete actions such as 'create archetypes, define components, schedule parallel jobs, configure Burst compilation, query entities with SystemAPI'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Unity ECS/DOTS) and some general actions ('building data-oriented games, optimizing performance, working with large entity counts'), but doesn't list specific concrete actions like 'create archetypes, schedule parallel jobs, define IComponentData structs, configure Burst compilation'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Master Unity ECS with DOTS, Jobs, and Burst for high-performance game development) and 'when' (explicit 'Use when' clause covering building data-oriented games, optimizing performance, or working with large entity counts). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Unity ECS', 'Entity Component System', 'DOTS', 'Jobs', 'Burst', 'high-performance', 'data-oriented', 'entity counts'. These are terms Unity developers naturally use when seeking help with this system. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology terms (Unity ECS, DOTS, Jobs, Burst) that clearly separate it from general Unity skills, general game development skills, or other ECS frameworks. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent, executable Unity ECS code examples covering a comprehensive range of patterns, which is its primary strength. However, it is far too verbose for a SKILL.md—it reads more like a tutorial or reference manual than a concise skill file. It explains concepts Claude already knows, dumps all patterns inline without progressive disclosure, and lacks workflow sequencing or validation steps.
Suggestions
Reduce the SKILL.md to a concise overview with 1-2 key patterns inline, and move the remaining 6+ patterns into separate referenced files (e.g., PATTERNS.md, BAKING.md, JOBS.md).
Remove the 'When to Use This Skill' section, the ECS vs OOP comparison table, and the 'Core Concepts' definitions—Claude already knows these concepts.
Add a workflow section showing the typical sequence for building an ECS feature: define components → implement system → set up baking → validate with Profiler, including common error patterns and how to fix them.
Cut the 'Best Practices' do's/don'ts list to only non-obvious items that are specific to Unity DOTS gotchas, removing generic advice like 'Profile with Profiler' and 'Don't over-architect'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. The ECS vs OOP comparison table, the 'Core Concepts' section explaining what entities/components/systems are, and the 'When to Use This Skill' section all explain things Claude already knows. Many patterns are exhaustively detailed when a representative subset would suffice. | 1 / 3 |
Actionability | All code examples are fully executable C# with proper using statements, complete method signatures, and realistic implementations. Patterns cover the full spectrum from basic components to spatial hashing with copy-paste ready code. | 3 / 3 |
Workflow Clarity | Patterns are presented as isolated examples rather than a sequenced workflow. There's no guidance on the order of implementation (e.g., define components → create systems → set up baking → test), and no validation checkpoints for common failure modes like Burst compilation errors or structural change issues. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of code with 8 detailed patterns all inline. The content would benefit enormously from splitting patterns into separate files with the SKILL.md serving as an overview. External links at the bottom are just general documentation, not structured references to companion files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (629 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.