test-environment

Test environment system (authored DomeGradient and IBLGradient, component schemas) against the poke example using the iwsdk CLI.

Quality

67%

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-environment/SKILL.md

Quality

Content

77%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 body is a strongly actionable, well-sequenced test procedure with executable commands, explicit assertions, and recovery feedback loops. Its main weaknesses are mild redundancy (the boolean caveat repeated) and a monolithic structure with no progressive disclosure.

Suggestions

Remove the duplicated JSON-boolean warning: keep it once (the Known Issues anchor) and link from the intro instead of restating.

Extract the per-suite expected-value tables or known-issues into a reference file (e.g., references/assertions.md) and link to it, giving the overview a one-level-deep progressive disclosure structure.

Tighten the template summary table and repeated IMPORTANT headers to reduce structural verbosity.

Dimension	Reasoning	Score
Conciseness	The body is actionable and assumes Claude's competence (no basic-concept padding), but the JSON-boolean caveat is duplicated (intro and "Known Issues") and several IMPORTANT blocks and the template summary table add mild redundancy.	2 / 3
Actionability	Every suite gives fully executable `npx iwsdk` commands with exact input JSON, plus expected-value tables and copy-paste-ready assertions.	3 / 3
Workflow Clarity	A clear Step 1–5 sequence with per-suite assertions as checkpoints, a Recovery section with retry-once feedback loop, and explicit failure-skip handling for fragile server operations.	3 / 3
Progressive Disclosure	No bundle files exist and the procedure is self-contained and well-sectioned, but it is a single monolithic document with no reference splitting or navigation to deeper material.	2 / 3
	Total	10 / 12 Passed

Description

57%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, naming concrete components and the tool, but it omits any explicit trigger/"Use when" guidance and describes a single action rather than enumerating capabilities. Adding a natural trigger clause would lift the completeness and trigger-term dimensions.

Suggestions

Append a "Use when..." clause naming natural user phrases (e.g., "Use when verifying the environment system, checking DomeGradient/IBLGradient defaults, or validating component schemas against the poke example").

List multiple concrete actions the skill performs (e.g., "Verifies authored environment components, checks system/component registration, validates scene hierarchy, and modifies ECS data") instead of the single verb "Test".

Soften jargon with at least one common-sense phrase a user would naturally say.

Dimension	Reasoning	Score
Specificity	Names concrete domain objects ("DomeGradient and IBLGradient, component schemas") and tool ("iwsdk CLI") but describes a single action ("Test ... against the poke example") rather than listing multiple specific actions.	2 / 3
Completeness	Clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Contains some relevant terms a user might say ("Test environment system", "poke example") but leans on technical jargon (component names) and lacks common natural variations.	2 / 3
Distinctiveness Conflict Risk	Highly specific to authored DomeGradient/IBLGradient components and the poke fixture via iwsdk, giving it a clear niche unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 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-environment/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.