unity-ecs-patterns

Production patterns for Unity's Data-Oriented Technology Stack (DOTS) including Entity Component System, Job System, and Burst Compiler.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/unity-ecs-patterns/SKILL.md

The canonical home for this skill is unity-ecs-patterns in rmyndharis/antigravity-skills

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.

The body is admirably concise and well-sectioned but almost content-free: instructions are generic boilerplate and the single progressive-disclosure reference is a broken path. It needs real, ECS-specific actionable guidance.

Suggestions

Replace the generic Instructions with concrete ECS guidance, e.g. archetype/component design, IJobChunk scheduling, and Burst `[BurstCompile]` annotations, or at minimum an executable code snippet.

Create the referenced resources/implementation-playbook.md (or correct the path to an existing bundle file) so the progressive-disclosure pointer actually resolves.

Add an explicit validation checkpoint for batch entity operations, e.g. "After structural changes, run EntityQuery.ToComponentDataArray and verify chunk counts before proceeding."

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; every section is terse and earns its place, matching the "lean and efficient; assumes Claude's competence" anchor.	5 / 5
Actionability	The Instructions are generic boilerplate ("Apply relevant best practices and validate outcomes", "Provide actionable steps and verification") with no concrete code, commands, or ECS-specific steps, and the only detailed pointer ("open resources/implementation-playbook.md") references a file that does not exist in the bundle.	2 / 5
Workflow Clarity	A rough sequence is present (clarify goals, apply practices and validate, provide steps and verification) and validation is mentioned, but checkpoints are only implicit and the steps are not ECS-specific, fitting the "steps listed but validation gaps; checkpoints missing or implicit" anchor.	3 / 5
Progressive Disclosure	Section structure is clean and the reference is clearly signaled, but it points to resources/implementation-playbook.md which is absent (no references/, scripts/, assets/, or resources/ bundle exists), leaving a broken navigation path that fits the "some structure but references not cleanly resolved" band.	3 / 5
	Total	13 / 20 Passed

Description

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

The description is distinctive and on-niche but action-light and lacks an explicit trigger clause. It reads more as a domain label than a capability statement, capping completeness and specificity.

Suggestions

Add concrete action verbs, e.g. "Architect, convert, and optimize Unity game systems using ECS, the Job System, and Burst."

Append a "Use when..." clause naming natural triggers (e.g. "Use when the user mentions ECS, DOTS, Jobs, Burst, or converting OOP Unity code to data-oriented systems").

Include common shorthand synonyms ("ECS", "DOTS", "game performance") to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Production patterns for Unity's Data-Oriented Technology Stack (DOTS) including Entity Component System, Job System, and Burst Compiler" names the domain and its subsystems but states no concrete actions (no build/optimize/convert verbs), matching the anchor that names the domain with minimal or generic actions.	2 / 5
Completeness	It gives a clear "what" (production patterns for DOTS / ECS / Jobs / Burst) but contains no "Use when..." clause or equivalent trigger guidance, so per the guidelines completeness is capped at 3 with a clear what but missing when.	3 / 5
Trigger Term Quality	It surfaces natural domain terms a Unity developer would actually say ("Unity", "DOTS", "Entity Component System", "Job System", "Burst Compiler"), giving good keyword coverage though it misses common shorthand like "ECS" and "game performance".	4 / 5
Distinctiveness Conflict Risk	The narrow Unity DOTS/ECS niche is clearly distinguishable from other skills and unlikely to trigger for the wrong skill, matching the "clear niche with distinct triggers; minimal conflict risk" anchor.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/unity-ecs-patterns/SKILL.md
Commit: 900c504

Reviewed: 7 hours 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.