Conciseness

The body is dominated by complete code with terse inline comments (e.g., '// Component: Pure data, no methods', '// Structural changes... require command buffers') and avoids tutorial padding, but it spends tokens on concepts Claude already knows — the 'ECS vs OOP' comparison table and the DOTS Components glossary ('Entity: Lightweight ID (no data)') — and the Performance Tips section restates patterns already demonstrated above ('Use Burst everywhere', 'Prefer IJobEntity', 'Schedule parallel'). That matches anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') — above anchor 3's more pervasive looseness, below anchor 5's every-token-earns-its-place.

Actionability

All eight patterns give complete, copy-paste-ready C# using the current Entities API (SystemAPI.Query, ISystem with [BurstCompile], EntityQueryBuilder, ECB singletons and ParallelWriter, IAspect, Baker with TransformUsageFlags, IJobParallelFor with NativeParallelMultiHashMap), covering the common cases from setup through baking to parallel jobs. This matches anchor 5 ('fully executable; copy-paste ready code; specific examples cover the common cases') with no pseudocode gaps.

Workflow Clarity

This is a pattern catalog rather than a multi-step procedure, so sequence is expressed as organization: 'When to Use This Skill' gives selection criteria and patterns are labeled by escalating use case (Basic Setup → Systems → Queries → ECB → Aspect → Singleton → Baking → Jobs). A reader knows which pattern to reach for, but there is no explicit ordering guidance ('start with Pattern 1...') and no validation checkpoints — though none are required since no destructive or batch operations are instructed, so the cap at 3 does not apply. Fits anchor 4's 'clear sequence with most checkpoints present; minor gaps' better than anchor 3, whose steps are merely listed without navigable labeling.

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/ exist), so all ~620 lines live in SKILL.md. Section headers are clear (## Patterns with ### Pattern N, ## Best Practices, ## Resources), giving real structure, but content that clearly belongs in separate reference files — eight full code patterns plus performance tips — is entirely inlined, matching anchor 3 ('some structure... content that should be separate is inline'). It is above anchor 2 (which lacks section organization) but below anchor 4, where most bulk content would be split into referenced files; the >50-line simple-skill exception does not apply at this size.

Specificity

"Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development" names the domain and its technologies, but the only action verb is the generic "Master" — no concrete capabilities (e.g., 'author components and systems', 'bake GameObjects', 'parallelize with jobs') are enumerated. The phrase lists tools and use cases rather than specific actions, matching anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); it is above anchor 2 because the use cases ("building data-oriented games, optimizing performance, or working with large entity counts") are concrete, and below anchor 4 because no executable capability list is given.

Completeness

Both halves are present: a what ("Master Unity ECS... with DOTS, Jobs, and Burst for high-performance game development") and an explicit when ("Use when building data-oriented games, optimizing performance, or working with large entity counts"), which satisfies the 'Use when...' requirement so it is not capped at 3. However the 'what' is goal-oriented rather than action-explicit and the 'when' triggers are broad, matching anchor 4 ('both present; when could be more explicit or specific') rather than anchor 5's fully concrete trigger phrases.

Trigger Term Quality

Triggers include "Unity ECS", "DOTS", "Jobs", "Burst", "data-oriented", "optimizing performance", "large entity counts" — natural phrases a Unity developer would say. It misses a few common variations ("entity component system" is only in parentheses, no "job system", "entities package", or "convert to ECS" phrasing), so it fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym list, and clearly exceeds anchor 3's partial coverage.

Distinctiveness Conflict Risk

"Unity ECS", "DOTS", "Burst", and "large entity counts" form a clear niche with distinct triggers; no other plausible skill overlaps with Unity's DOTS stack. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk') and exceeds anchor 4 because even closely related skills (general Unity, C# performance) would not be selected by these terms.