CtrlK
BlogDocsLog inGet started
Tessl Logo

test-ecs-core

Test ECS core functionality (system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots) against the poke example using the iwsdk CLI.

67

Quality

81%

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

88%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 content is a highly actionable, well-sequenced test harness with explicit validation checkpoints and recovery loops, and it is token-efficient for its scope. The only structural consideration is that the single file is long and the assertion reference tables could be externalized, but as a self-contained runbook it navigates easily.

DimensionReasoningScore

Conciseness

The body is almost entirely executable commands, exact JSON payloads, and assertion values with no padding or explanations of known concepts; only minor trimmable redundancy remains (the LevelTag 'ecs find' command repeated across suites 3 and 7, and several restated IMPORTANT notes).

4 / 5

Actionability

Every step is a copy-paste-ready 'npx @iwsdk/cli' command with exact --input-json payloads, expected output shapes, concrete assertion values and tolerances (e.g. 'localPosition matches [0, 2, -1] within tolerance of 0.01'), covering all common cases including failure branches.

5 / 5

Workflow Clarity

Steps 1-5 are explicitly sequenced with validation checkpoints (connectivity check, error/warn log assertion, per-suite PASS/FAIL table), explicit failure escalation ('report FAIL for all suites and skip to Step 5'), and a Recovery section with a validate-retry-give-up feedback loop.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear per-suite headings plus Known Issues and Recovery sections; no bundle files exist to reference. At ~385 lines the expected-value tables (system priorities, component schemas) could arguably be split into a reference file, leaving minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

75%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 specific, concrete, and highly distinguishable, but it omits any 'when to use' trigger guidance, which is the rubric's explicit completeness cap. Adding a Use-when clause with natural trigger phrases would also lift trigger term quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user asks to test, verify, or validate ECS core behavior, or mentions the poke example, iwsdk CLI, or ECS test suites.'

Add a few natural trigger synonyms users might say ('test the ECS', 'verify systems', 'run the poke tests') to broaden keyword coverage beyond the enumerated capability names.

Optionally mention the suite selector from argument-hint (e.g. 'supports per-suite runs') so the description reflects the skill's selective-run capability.

DimensionReasoningScore

Specificity

Names the domain ('Test ECS core functionality') and enumerates seven concrete actions ('system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots') plus a concrete target ('against the poke example using the iwsdk CLI'), giving comprehensive coverage with no gaps.

5 / 5

Completeness

Has a clear and detailed 'what' but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3; 'when' is entirely absent rather than weakly implied.

3 / 5

Trigger Term Quality

Good natural keywords ('ECS', 'system registration', 'Transform sync', 'pause/step/resume', 'entity discovery', 'snapshots') but no trigger phrases or synonyms describing when a user would invoke it, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

Highly distinct niche: 'against the poke example using the iwsdk CLI' pins the skill to a specific example app and CLI, so it is unlikely to trigger for the wrong skill.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
facebook/immersive-web-sdk
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.