CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/game-development/skills/unity-ecs-patterns/SKILL.md

The canonical home for this skill is unity-ecs-patterns in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A code-rich, highly actionable ECS/DOTS pattern reference whose main weaknesses are length/conciseness and the absence of progressive disclosure — everything is inlined in one large file with no separate reference bundles.

Suggestions

Move the detailed patterns (e.g. baking, jobs with native collections, aspects) into separate reference files under references/ and keep SKILL.md as a concise overview with one-level-deep links, improving progressive_disclosure and conciseness.

Trim redundant examples — the two movement-system variants (foreach vs explicit IJobEntity) restating the same transform update could be consolidated to one with a brief note on the alternative.

Add a short validation/profiling checkpoint (e.g. confirm Burst compilation is active, check chunk utilization in the Profiler) after the performance section to strengthen workflow clarity for optimization work.

DimensionReasoningScore

Conciseness

Mostly dense, useful code but the 624-line body includes redundant worked examples (two movement systems restating the same idea) and inline explanations of basics Claude already knows; it could be tightened.

3 / 5

Actionability

Provides extensive copy-paste-ready, executable C# across eight patterns covering components, systems, queries, ECBs, aspects, singletons, baking, and jobs — specific examples span the common cases.

5 / 5

Workflow Clarity

Organized as a patterns catalog with clear sections rather than a sequenced process; no explicit validation checkpoints or feedback loops, which fits a reference skill but misses the higher anchors.

3 / 5

Progressive Disclosure

Section headers give decent navigation, but no bundle files exist and all 624 lines (eight full patterns, perf tips, best practices) are inlined in SKILL.md rather than split into one-level-deep reference files.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly covers both what the skill does and when to use it with concrete, natural trigger phrases. Voice is imperative (not first/second person), specific, and low conflict risk.

DimensionReasoningScore

Specificity

Names the domain (Unity ECS) and several specific concrete sub-areas ('DOTS, Jobs, and Burst', 'building data-oriented games, optimizing performance, large entity counts'); minor gaps in coverage versus the level-5 anchor's exhaustive action list.

4 / 5

Completeness

Clearly states what it does ('Master Unity ECS ... with DOTS, Jobs, and Burst for high-performance game development') and explicitly answers when with a 'Use when ...' clause listing concrete triggers.

5 / 5

Trigger Term Quality

Includes natural terms users say ('Unity ECS', 'DOTS', 'Jobs', 'Burst', 'data-oriented games', 'optimizing performance', 'large entity counts'); a few synonyms or file/extension-style variants are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Unity DOTS/ECS) with distinct, specific triggers; minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (629 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.