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.
57
66%
Does it follow best practices?
Impact
—
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.
The description has strong trigger terms, clear completeness with an explicit 'Use when' clause, and excellent distinctiveness within the Unity ECS niche. Its main weakness is the lack of specific concrete actions—it describes the domain well but doesn't enumerate particular tasks the skill enables. The word 'Master' at the beginning is slightly informal/imperative rather than third-person descriptive.
Suggestions
Replace 'Master Unity ECS' with third-person phrasing like 'Guides development with Unity ECS' and add specific concrete actions such as 'create archetypes, define components, schedule parallel jobs, configure Burst compilation, manage entity queries'.
| 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' (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', 'large entity counts', 'optimizing performance'. 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, with domain-specific triggers like 'Entity Component System', 'DOTS', 'Jobs', 'Burst' that are unlikely to conflict with general Unity skills or other game development 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.
This skill is essentially a comprehensive Unity ECS reference manual crammed into a single file. While the code examples are excellent — fully executable, well-structured, and covering the major DOTS patterns — the file is far too verbose for a skill, explains concepts Claude already knows, and fails to organize content into a navigable hierarchy. It would benefit greatly from being restructured into a brief overview with references to separate pattern files.
Suggestions
Reduce the SKILL.md to a concise overview (~50-80 lines) covering the most essential pattern (basic ISystem + component) and move the remaining 7 patterns into separate bundle files (e.g., patterns/ecb.md, patterns/aspects.md, patterns/baking.md) with clear links.
Remove the 'When to Use This Skill' section and the ECS vs OOP comparison table — Claude already understands these concepts and they consume tokens without adding actionable value.
Add a workflow section that sequences the steps for building an ECS feature: define components → implement system → set up baking → test with Profiler → optimize with Burst/Jobs, with validation checkpoints at each stage.
Remove or drastically condense the 'Core Concepts' section that defines Entity, Component, System, World, Archetype, and Chunk — these are basic DOTS concepts Claude already knows.
| 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' list all explain things Claude already knows. The sheer volume of code patterns (8 full patterns plus performance tips and best practices) makes this a reference manual rather than a lean skill file. Much of this could be trimmed or split into separate files. | 1 / 3 |
Actionability | Every pattern provides fully executable, copy-paste-ready C# code with proper using statements, complete struct/class definitions, and realistic implementations. The code covers components, systems, queries, ECBs, aspects, singletons, baking, and jobs with native collections — all concrete and specific. | 3 / 3 |
Workflow Clarity | The patterns are presented as isolated code blocks without a clear workflow sequence for building an ECS project. There's no guidance on the order of operations (e.g., define components → create systems → set up baking → test), no validation checkpoints, and no error recovery steps. The 'Best Practices' section lists do's and don'ts but doesn't integrate them into a workflow. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content — 8 full code patterns, performance tips, and best practices all inline with no bundle files to offload detail into. The patterns (spatial hashing, aspects, baking) could easily be separate reference files linked from a concise overview. External links at the bottom are to Unity docs, not to structured bundle 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
895269a
- 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.