test-environment

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

Quality

73%

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

88%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 an excellent executable test procedure: fully concrete commands with exact assertions, explicit validation checkpoints, failure paths, and a bounded recovery loop. Its only weaknesses are minor duplication (the boolean-coercion warning stated twice) and the lack of any content split across reference files for the long suite details.

Dimension	Reasoning	Score
Conciseness	The body is dense and command-driven with expected values in compact tables and no explanations of concepts Claude already knows; however, the JSON-boolean warning appears twice (top 'IMPORTANT' block and again under 'Known Issues'), and the intro configuration block slightly duplicates the per-step instructions — minor trimming opportunities keep it below the lean-anchor score of 5.	4 / 5
Actionability	Every step is a fully executable, copy-paste-ready command with exact JSON payloads, timeouts, and concrete expected values (e.g., exact color vectors in tables, priority 0, query entity counts), covering all common cases including failure paths.	5 / 5
Workflow Clarity	The sequence is explicitly numbered (install → start server → verify connectivity → pre-test setup → suites → cleanup), each suite has explicit pass/fail assertions with actual-vs-expected reporting, and there is a dedicated Recovery section with a bounded retry loop ('Only give up after one retry attempt per suite') — a textbook validation feedback loop.	5 / 5
Progressive Disclosure	No bundle files exist and sections are well organized (Steps, Suites, Recovery, Known Issues) with clear headers, but the ~280-line monolithic body inlines suite detail (expected-value tables, known-issues workarounds) that could be split into reference files — good structure with minor organization gaps rather than ideal content splitting.	4 / 5
	Total	18 / 20 Passed

Description

57%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 highly specific to its project niche and clearly states what it does, but it lacks any 'Use when...' trigger guidance and relies solely on technical jargon rather than natural user phrasing. Adding an explicit when-to-use clause with natural trigger terms would raise completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user asks to run the poke environment tests, verify DomeGradient/IBLGradient components, or check environment system registration.'

Include natural-language synonyms users might say (e.g., 'environment tests', 'poke example', 'run the env suites') alongside the technical component names.

Optionally enumerate the concrete verification actions (system registration, component registration, scene hierarchy, ECS modification, stability) to broaden capability coverage.

Dimension	Reasoning	Score
Specificity	The description names a single concrete action ('Test environment system') with specific targets ('authored DomeGradient and IBLGradient, component schemas', 'the poke example', 'the iwsdk CLI'), which matches the anchor for naming the domain with 1-2 concrete actions but not comprehensive coverage — it only tests, without enumerating what verification covers (registration, hierarchy, stability).	3 / 5
Completeness	It has a clear 'what' (testing the authored environment system against the poke example), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Terms like 'DomeGradient', 'IBLGradient', 'poke example', and 'iwsdk CLI' are relevant to this project but are technical jargon with no natural-language variations or synonyms (e.g., 'run the poke env tests', 'verify the environment components'), matching the anchor for some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The description is anchored to project-specific artifacts (DomeGradient, IBLGradient, poke example, iwsdk CLI), giving it a clear niche with distinct triggers and minimal conflict risk with other skills — it would not fire for unrelated tasks.	5 / 5
	Total	14 / 20 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: 0778f51

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