CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

84%

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.

A strong operational test-runner skill: fully executable commands, explicit assertions, validation checkpoints, and a retry policy throughout. Its only weaknesses are minor command-string repetition and inline content (known issues) that could be moved to a reference file.

DimensionReasoningScore

Conciseness

The body is dense and command-focused with no explanation of concepts Claude already knows (no ECS primer, no library overview), but it repeats the full 'npx @iwsdk/cli ... 2>/dev/null' prefix on every command and has slight overlap between the Recovery and Known Issues sections that could be trimmed.

4 / 5

Actionability

Every suite provides copy-paste-ready commands with exact --input-json payloads, concrete expected values (e.g., 'LocomotionSystem | -5', 'framesAdvanced === 5', tolerance 0.01), and placeholders like <test-start-ms> and <UUID> that are explicitly derived in prior steps.

5 / 5

Workflow Clarity

A clear 5-step sequence with explicit 'Assert:' validation checkpoints after each command, defined failure paths ('report FAIL for all suites and skip to Step 5'), and a concrete retry feedback loop ('Only give up after one retry attempt per suite'). This matches the anchor with explicit validation steps and error-recovery loops, not the level below where checkpoints are merely present.

5 / 5

Progressive Disclosure

The single file is well-sectioned with clear ## / ### headers, tables, and a coherent linear procedure, and no bundle files exist; however, the ~40-line Known Issues & Workarounds section is content that could arguably be split into a reference file, keeping it just below the well-signaled one-level-deep ideal.

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.

A specific, highly distinctive description that clearly states what the skill does across seven functional areas. Its main gap is the absence of any 'when to use' trigger guidance, which limits discoverability and caps completeness.

Suggestions

Add an explicit trigger clause, e.g., 'Use when asked to run, verify, or regression-test ECS core functionality in an IWSDK project.'

Include a few natural user phrasings such as 'run the ECS tests' or 'verify the poke example' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description enumerates seven concrete capabilities — 'system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots' — giving comprehensive, specific coverage rather than the minor-gaps profile of the level below.

5 / 5

Completeness

It clearly answers 'what' (tests seven named ECS areas against the poke example), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the 'when' is only weakly implied by the argument-hint.

3 / 5

Trigger Term Quality

Good keyword coverage ('ECS', 'system registration', 'Transform sync', 'pause/step/resume', 'entity discovery', 'snapshots', 'poke example', 'iwsdk CLI'), but it lacks natural synonyms and phrasing variations users might say such as 'run tests', 'verify', or 'regression', so it does not reach the comprehensive-with-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The phrase 'against the poke example using the iwsdk CLI' pins a clear niche with distinct triggers, making conflict with unrelated skills minimal.

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

Path

.claude/skills/test-ecs-core/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.