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.

68

Quality

83%

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

92%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 highly actionable and well-structured, with executable commands, precise assertions, and strong validation/recovery guidance throughout. The only minor gap is a little prose that could be tightened for token efficiency.

Suggestions

Consolidate the repeated tool-call conventions into a single upfront block to reduce duplicated prose across suites.

Tighten the Known Issues section to one-line bullets to shave tokens without losing the workaround signal.

Consider a short 'Expected output' snippet for one representative command to make assertion parsing even more concrete.

DimensionReasoningScore

Conciseness

The body is mostly efficient — concrete commands and assertions with little concept-level padding — but sections like the repeated tool-call conventions and Known Issues prose could be trimmed slightly.

4 / 5

Actionability

Every suite gives copy-paste-ready 'npx iwsdk' commands with exact --input-json payloads and explicit assertions (expected values, tolerances, counts), fully covering the common cases.

5 / 5

Workflow Clarity

A clear five-step sequence (install, start server, connectivity, run suites, cleanup) with explicit validation checkpoints and a retry-once feedback loop per suite for transient errors.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained; content is well-organized into clearly signaled suites with no nested references, which is appropriate for a single-purpose test runner.

5 / 5

Total

19

/

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 and distinctive, enumerating concrete ECS capabilities and pinning the scope to a particular example and CLI. Its main weakness is the absence of any explicit 'when to use' guidance.

Suggestions

Add a 'Use when...' clause (e.g. 'Use when validating ECS core behavior after changes to system registration, component schemas, or the Transform sync pipeline') to lift completeness above 3.

Include a couple of natural user-voice synonyms (e.g. 'ECS systems', 'component schemas', 'entity queries') to broaden trigger-term coverage.

Consider mentioning file extensions or artifact names a user might reference to further reduce conflict risk with adjacent test skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots' — giving comprehensive coverage of what the skill tests.

5 / 5

Completeness

Provides a clear 'what' (testing ECS core across seven areas) but has no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains natural domain keywords like 'ECS', 'Transform sync', 'pause/step/resume', and 'snapshots' that a user would plausibly say, but a few natural synonyms or phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

The phrase 'against the poke example using the iwsdk CLI' carves out a clear, narrow niche with minimal risk of triggering 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.

Validation15 / 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.