CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

72%

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 ./plugins/game-development/skills/unity-ecs-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

Well-structured overview with excellent progressive disclosure and decent token efficiency, but the main body itself is not actionable — it contains no code or commands and no workflow for applying the patterns. The concrete content lives entirely in references/details.md.

Suggestions

Include at least one minimal, copy-paste-ready C# example in the body (e.g. a component plus an ISystem) so the skill is actionable before reading references/details.md.

Add a short sequenced workflow for the most common task, such as converting a MonoBehaviour to ECS (define components -> write ISystem -> schedule with Job/Burst -> batch structural changes via ECB).

Remove or compress the generic ECS-vs-OOP comparison table, which explains a tradeoff Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly lean bullets and a tight glossary, but the "ECS vs OOP" comparison table re-explains a tradeoff Claude already knows and could be trimmed.

4 / 5

Actionability

The body contains no executable code or commands at all — the Do's/Don'ts ("Use ISystem over SystemBase", "Batch structural changes - Use ECB") are high-level hints with the actual examples deferred entirely to references/details.md, leaving only minimal concrete guidance in the main file.

2 / 5

Workflow Clarity

There is no sequence or process at all — no "how to start" path, no OOP-to-ECS conversion steps, and no guidance on when to read references/details.md relative to a task — so it sits between a rough sequence with gaps and organized-but-checkpoint-free content.

3 / 5

Progressive Disclosure

The body is a genuine overview that correctly splits the bulk patterns into a verified, one-level-deep reference ("Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient"), with no nesting or buried references.

5 / 5

Total

14

/

20

Passed

Description

73%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, distinctive description with an explicit and well-targeted trigger clause. Its main weakness is the generic "Master" verb, which describes scope instead of the concrete capabilities the skill provides.

Suggestions

Replace the generic verb "Master" with 1-2 concrete capabilities, e.g. "Implements Unity ECS production patterns for movement, spawning, and combat systems using DOTS, Jobs, and Burst."

Add natural trigger variations such as "thousands of entities" or "converting MonoBehaviour code to ECS" to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain precisely ("Unity ECS (Entity Component System) with DOTS, Jobs, and Burst") but its only action verb is the generic "Master", which names scope rather than concrete capabilities like build, optimize, or convert.

3 / 5

Completeness

The "when" is explicit and concrete ("Use when building data-oriented games, optimizing performance, or working with large entity counts"), but the "what" ("Master Unity ECS...") describes scope rather than what the skill concretely does, so it falls short of the anchor-5 example's fully explicit what-and-when pairing.

4 / 5

Trigger Term Quality

"Unity ECS", "DOTS", "Jobs", "Burst", "data-oriented games", "optimizing performance", and "large entity counts" are terms users would naturally say, though common variations like "thousands of entities" or "game performance" are absent.

4 / 5

Distinctiveness Conflict Risk

The Unity DOTS/ECS niche with named sub-technologies is highly distinct with concrete triggers; only "optimizing performance" is broadly phrased, and it is anchored by the surrounding Unity-specific terms.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/game-development/skills/unity-ecs-patterns/SKILL.md

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.