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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The content is highly actionable and tightly written, with executable commands, explicit assertions, and strong validation/recovery feedback loops across a clear 5-step workflow. Its only weakness is progressive disclosure: the entire 8-suite spec is a single inline file with no references to defer detail to.

Dimension	Reasoning	Score
Conciseness	The body is lean command-and-assertion prose with no concept explanations Claude already knows; each token (priority tables, expected counts, JSON payloads) earns its place, satisfying the score-3 'lean and efficient' anchor.	3 / 3
Actionability	Every step gives copy-paste-ready `npx iwsdk ... --input-json '<JSON>'` commands plus exact assertions (e.g. 'paused === true', 'framesAdvanced === 5'), matching the fully executable, copy-paste-ready anchor.	3 / 3
Workflow Clarity	Steps 1–5 are explicitly sequenced with per-suite numbered sub-steps, validation checkpoints ('Parse the JSON output and verify assertions before moving to the next command'), and a Recovery feedback loop (stop → restart → re-run → retry, 'Only give up after one retry attempt'), fulfilling the score-3 anchor.	3 / 3
Progressive Disclosure	No references/scripts/assets bundle exists, so all 8 suites live inline in one ~370-line SKILL.md; it is well-sectioned but content that could be split into per-suite reference files is monolithic, fitting the score-2 'content that should be separate is inline' anchor rather than the one-level-deep reference structure of score 3.	2 / 3
	Total	11 / 12 Passed

Description

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 is specific and distinctive, naming concrete ECS capabilities bound to a particular example and CLI, but it omits any 'when to use' trigger guidance and relies on domain jargon rather than natural user phrasing. Adding a 'Use when...' clause with natural-language triggers would raise the weaker dimensions.

Suggestions

Append a 'Use when ...' clause with natural trigger phrasing, e.g. 'Use when the user wants to verify ECS behavior, run regression checks on the poke example, or validate iwsdk system/component/transform operations.'

Add common-language variations of trigger terms (e.g. 'entity-component-system', 'ECS tests', 'iwsdk poke regression') so users who don't use exact jargon still match.

Keep the concrete capability list but lead with the user-facing intent so the description opens with 'when' as well as 'what'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots' — matching the score-3 anchor that enumerates specific capabilities rather than vague language.	3 / 3
Completeness	It clearly answers 'what' (testing ECS core functionality with enumerated capabilities) but never states 'when' Claude should invoke it; the judging guidelines cap completeness at 2 when a 'Use when...' clause is absent.	2 / 3
Trigger Term Quality	Terms like 'ECS core', 'Transform sync', 'pause/step/resume', and 'iwsdk CLI' are relevant to the niche but are technical jargon with no common natural-language variations; it lacks the broad 'Use when...' trigger phrasing users might say.	2 / 3
Distinctiveness Conflict Risk	The narrow pairing of 'ECS core functionality ... against the poke example using the iwsdk CLI' carves a clear 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
Commit: 42af866

Reviewed: 6 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.