CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ecs-design

Use when designing components, systems, or entity structures for jecs in Roblox. Use when deciding if data should be one component or multiple, when archetype transitions seem expensive, or when choosing entity members vs relationships.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured decision-reference skill: the body stays a lean overview of decision rules and pushes depth to five real, clearly-signaled reference files. The main gaps are mild redundancy across the three summary tables and the absence of any jecs code snippets to make the API-level rules (.cached(), with/without) fully executable.

DimensionReasoningScore

Conciseness

The body is ~70 lines of dense tables with no padding or explanation of generic ECS background Claude already knows — the 'columnar database' table is skill framing, not a tutorial. It falls short of anchor 5 only because the same rules repeat across sections ('entity members vs relationships' and 'split or combine' each appear in the Quick Decision Guide, Common Mistakes, and Key Principles).

4 / 5

Actionability

For an instruction-only skill the guidance is concrete and directly usable: "Only if it needs per-instance state that changes over time", "'Is there a system that needs A but not B?'", "Never call `.cached()` inside a system", "Create cached queries at module scope", "Tags for stable classification (free to add/remove), data for state". It stops short of anchor 5 because jecs-specific syntax is named (with/without filters, .cached()) but never shown, leaving minor gaps in executable detail.

4 / 5

Workflow Clarity

This is a decision-guide skill with no multi-step process and no destructive/batch operations, so no validation checkpoints are required. The lookup path is clear (mental model → reference tables → decision rules → mistakes), and the Quick Decision Guide gives direct answers to the exact questions a user would bring. It misses anchor 5 under the simple-skill exception because there is no explicit routing for which reference file to consult for a given question beyond the topic tables.

4 / 5

Progressive Disclosure

The body is a lean overview and every deep-dive lives in references/: all five files in references/ are linked from well-organized tables (topic + one-line description + link), every referenced path exists, and references are exactly one level deep — a direct match for anchor 5 ('clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation').

5 / 5

Total

17

/

20

Passed

Description

78%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, well-targeted description: it opens with a domain-anchored 'Use when' clause and adds three concrete design-trigger scenarios that users of jecs would naturally phrase this way. Its only weakness is that the 'what' is implied through the trigger activities rather than stated as an explicit capability sentence.

DimensionReasoningScore

Specificity

The description names the domain ("for jecs in Roblox") and several concrete design actions: "deciding if data should be one component or multiple", "when archetype transitions seem expensive", "choosing entity members vs relationships". These are specific, decision-level actions rather than generic verbs, though coverage of the skill's full scope (queries, caching, fragmentation) is only partial, matching the anchor 'lists several specific actions; minor gaps in coverage' rather than the comprehensive 5.

4 / 5

Completeness

The 'when' is explicit and highly specific — three concrete 'Use when...' clauses with real trigger scenarios. The 'what' is conveyed through the named design activities ("designing components, systems, or entity structures") rather than a standalone capability statement, so it is present but slightly implicit, placing this between anchor 3 (clear what, weak when — the inverse situation) and anchor 5 (both fully explicit).

4 / 5

Trigger Term Quality

Natural terms a jecs user would say are well covered: "components", "systems", "entity structures", "archetype", "relationships". It sits at anchor 4 ('good keyword coverage; a few natural terms missing') because some plausible user phrasings (e.g., 'split', 'fragmentation', 'performance', 'query design') appear in the body but not the description.

4 / 5

Distinctiveness Conflict Risk

"for jecs in Roblox" carves out a clear niche with domain-specific triggers (archetype transitions, entity members vs relationships) that no general-purpose skill would claim, matching anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

17

/

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

christopher-buss/skills

Path

skills/ecs-design/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.