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

72%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/test-ecs-core/SKILL.md

Quality

Discovery

67%

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 excels at specificity and distinctiveness by listing concrete ECS testing actions and naming the specific tool and target example. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Trigger terms are adequate but lean heavily on domain jargon.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to test or verify ECS functionality, debug entity-component systems, or run iwsdk CLI tests against the poke example.'

Include natural-language trigger variations such as 'entity component system testing', 'ECS debugging', or 'run poke tests' to improve matching against diverse user phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots. Also specifies the target (poke example) and tool (iwsdk CLI).	3 / 3
Completeness	Clearly answers 'what does this do' (test ECS core functionality with specific sub-features), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes relevant technical terms like 'ECS', 'system registration', 'components', 'Transform sync', 'snapshots', 'iwsdk CLI', and 'poke example'. However, these are fairly domain-specific and may miss natural user phrasings like 'test my game systems' or 'debug entity component system'.	2 / 3
Distinctiveness Conflict Risk	Highly specific niche: ECS testing against the poke example using the iwsdk CLI. This combination of domain (ECS), target (poke example), and tool (iwsdk CLI) makes it very unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

77%

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

This is a well-crafted, highly actionable test skill with excellent workflow clarity — every command is concrete, assertions are specific with expected values, and the sequencing includes validation checkpoints and recovery procedures. The main weakness is that all 8 test suites are inlined in a single long document rather than being split across referenced files, and there's some minor verbosity in the known issues section. Overall it's a strong skill that would reliably guide Claude through the complete ECS test process.

Suggestions

Consider splitting individual test suites into separate files (e.g., suite-1-system-registration.md) and referencing them from the main SKILL.md to improve progressive disclosure and reduce the monolithic document length.

Trim the Known Issues section — items like 'UUIDs change on reload' and 'entity indices change on reload' are already implied by the instructions to re-discover after reload.

Dimension	Reasoning	Score
Conciseness	The skill is fairly long but most content is necessary test specifications with concrete assertions. Some sections could be tightened (e.g., the recovery section and known issues repeat information Claude could infer), but overall the verbosity is justified by the complexity of 8 test suites with specific expected values.	2 / 3
Actionability	Every test suite provides exact CLI commands, specific assertion criteria with expected values (system names, priorities, entity counts, field types), and concrete JSON input parameters. Commands are copy-paste ready with clear expected outputs.	3 / 3
Workflow Clarity	The workflow is clearly sequenced from install → start server → verify connectivity → run suites → cleanup, with explicit validation at each step (check JSON output, verify assertions before proceeding). Recovery procedures with retry logic are well-defined, and the 'IMPORTANT' notes about running commands one at a time and using sleep provide critical guardrails.	3 / 3
Progressive Disclosure	The content is a monolithic ~300-line document with all 8 test suites inline. While the structure uses clear headers and horizontal rules, the detailed test specifications for each suite could benefit from being split into separate files with the SKILL.md serving as an overview. No bundle files are provided to offload content.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: facebook/immersive-web-sdk
Commit: 3a08b40

Reviewed: 10 minutes 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.