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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

A concise, well-organized overview that uses progressive disclosure effectively by deferring worked examples to a single clearly-signaled reference file. The body's main gap is the absence of any executable code or sequenced workflow, leaving actionability and workflow clarity below the top anchors.

Suggestions

Add one minimal copy-paste-ready snippet in the body (e.g. a basic ISystem + [BurstCompile] job) so the skill is actionable before reading the reference file.

Include a short ordered 'getting started' sequence (create components -> write ISystem -> schedule job -> bake GameObjects) with a profile/validate checkpoint to lift workflow clarity.

Trim the 'ECS vs OOP' comparison table, which restates concepts Claude already knows, to further sharpen conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean: a compact comparison table, a terse concept glossary, and concise Do/Don't lists with no padded prose, so every token earns its place.	3 / 3
Actionability	Guidance is specific ('Use ISystem over SystemBase', 'Batch structural changes - Use ECB') but the body itself contains no executable code; all real snippets are deferred to references/details.md, leaving it incomplete versus copy-paste-ready.	2 / 3
Workflow Clarity	The body is well organized into sections but is a patterns catalog rather than a sequenced process, with no explicit workflow steps or validation checkpoints, so it does not reach the top anchor.	2 / 3
Progressive Disclosure	The body is a genuine overview that clearly signals one-level-deep navigation to references/details.md (verified to exist), with detail appropriately split out and easy to find.	3 / 3
	Total	10 / 12 Passed

Description

90%

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, well-structured description with explicit 'Use when' triggers and a clear, distinctive niche. Its only weakness is that capability is framed as 'Master X' rather than a list of concrete actions, leaving specificity slightly below the top anchor.

Suggestions

Replace the 'Master Unity ECS ...' framing with 2-3 concrete verbs, e.g. 'Author ECS systems, schedule Burst-compiled jobs, and bake GameObjects into entities' to lift specificity to the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and tools (Unity ECS, DOTS, Jobs, Burst) but frames capability as 'Master Unity ECS' rather than enumerating concrete actions, so it stops at 'names domain and some actions'.	2 / 3
Completeness	Explicitly answers both what ('Master Unity ECS ... for high-performance game development') and when ('Use when building data-oriented games, optimizing performance, or working with large entity counts').	3 / 3
Trigger Term Quality	'Use when building data-oriented games, optimizing performance, or working with large entity counts' gives good coverage of natural phrases a user would say, plus domain keywords (DOTS, Jobs, Burst).	3 / 3
Distinctiveness Conflict Risk	The Unity ECS/DOTS niche with terms like 'DOTS, Jobs, and Burst' and 'large entity counts' is clearly distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: 5cc2549

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.