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, clearly targeting the Unity ECS/DOTS niche with an explicit 'Use when' clause. Its main weakness is that the 'what' portion is somewhat high-level ('Master Unity ECS') rather than listing specific concrete actions the skill enables, and the use of 'Master' as a verb feels slightly vague rather than action-oriented.
Suggestions
Replace 'Master Unity ECS' with specific concrete actions like 'Create and manage Unity ECS archetypes, schedule parallel Jobs, define IComponentData structs, configure Burst compilation, and optimize system queries.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Unity ECS/DOTS) and mentions some actions like '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' (Use when building data-oriented games, optimizing performance, or working with large entity counts) with an explicit 'Use when' clause. | 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', 'game development'. These cover the main terms a Unity developer would use when seeking ECS help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting Unity ECS/DOTS specifically, which is clearly separable from general Unity skills, general game development skills, or other engine-specific skills. The combination of ECS, DOTS, Jobs, and Burst creates a very specific trigger profile. | 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 comprehensive, executable Unity ECS code examples covering all major DOTS patterns, which is its primary strength. However, it is far too verbose for a SKILL.md file—it reads like a tutorial or reference manual rather than a concise skill guide. It lacks workflow sequencing, validation steps, and progressive disclosure structure, cramming everything into one massive file.
Suggestions
Reduce the SKILL.md to a concise overview with 2-3 core patterns (Basic ECS Setup, Systems with ISystem, ECB) and move advanced patterns (Aspects, Spatial Hashing, Baking, Jobs) to separate referenced files like PATTERNS_ADVANCED.md.
Remove the 'When to Use This Skill' section, the ECS vs OOP comparison table, and the 'Core Concepts' text block—Claude already understands these concepts.
Add a workflow section with clear sequencing: 1) Define components → 2) Create systems → 3) Set up baking → 4) Verify in Profiler, with explicit validation checkpoints for common failure modes like Burst compilation errors.
Trim the Best Practices section to only non-obvious gotchas (e.g., 'enableable components instead of add/remove for hot paths') rather than generic advice like 'profile with Profiler'.
| 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 single representative example 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 jobs, all copy-paste ready. | 3 / 3 |
Workflow Clarity | Patterns are presented as isolated code blocks without a clear workflow sequence for building an ECS project. There's no guidance on order of operations (define components → create systems → bake → test), no validation checkpoints, and no error recovery steps for common pitfalls like Burst compilation failures or native collection leaks. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of code patterns with no content split into separate files. At this length (~400+ lines), the detailed patterns for Aspects, Spatial Hashing, Baking, etc. should be in separate referenced files. The external links at the bottom are just generic documentation URLs, not structured skill references. | 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
6e3d68c
- 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.