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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/test-ecs-core/SKILL.md

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a lean, highly actionable test procedure with clear sequencing and validation checkpoints. Its main weakness is the lack of progressive disclosure — everything is inline with no reference files — though for a single-purpose test runner this is partly justified.

Suggestions

Consider moving the per-suite assertion tables and Known Issues into a separate reference file (e.g., references/assertions.md) linked from the main body to reduce inline bulk.

Extract the shared CLI invocation pattern and timeout guidance into a short reference so the body stays focused on the test sequence.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable commands and assertions and does not explain concepts Claude already knows; every section (setup, suites, recovery, known issues) earns its place.	3 / 3
Actionability	Every suite provides fully executable `npx iwsdk ...` commands with concrete JSON inputs and explicit expected assertion values, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced with validation checkpoints (connectivity check, per-suite assertions), plus a Recovery feedback loop and Known Issues section for error handling.	3 / 3
Progressive Disclosure	Content is well-organized into sections but is entirely monolithic with no references to separate files; large assertion tables and known-issue content live inline that could be split out.	2 / 3
	Total	11 / 12 Passed

Description

67%Weight 40%Scale 1-3

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, clearly enumerating the test suites and target example, but omits any explicit 'Use when...' trigger guidance. Adding a trigger clause would raise completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause such as 'Use when verifying ECS core behavior, running regression suites on the poke example, or when the user asks to test system registration, components, or Transform sync.'

Include more natural user-facing phrasing (e.g., 'test the poke example', 'ECS regression checks') alongside the technical terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots' — naming specific capabilities rather than vague language.	3 / 3
Completeness	Clearly states what the skill does, but provides no 'Use when...' clause or equivalent explicit guidance on when Claude should invoke it, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Contains domain-relevant terms ('ECS core', 'Transform sync', 'pause/step/resume') a user in this domain would say, but they lean technical and lack common natural variations or an explicit trigger clause.	2 / 3
Distinctiveness Conflict Risk	The narrow scope — testing ECS core against the poke example via the iwsdk CLI — is a distinct niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 0fb2195

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.