CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-environment

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

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 a strongly actionable, fully executable test procedure with explicit validation checkpoints, failure gates, and a bounded recovery loop. Its only weaknesses are mild redundancy (the boolean warning repeated three times) and a monolithic single-file layout where expected-value tables and known issues could be split into reference files.

DimensionReasoningScore

Conciseness

The body is command-first and lean — no explanations of concepts Claude already knows — but the boolean-type warning ("value must be a JSON boolean... Strings silently fail") is repeated three times (the top IMPORTANT block, the suite note, and the "Boolean values must be JSON booleans" Known Issues entry), which is minor padding that could be trimmed. Efficient overall, so it sits above anchor 3 but below the every-token-earns-its-place bar of anchor 5.

4 / 5

Actionability

Every step is a fully executable `npx @iwsdk/cli <subcommand> --input-json '{...}'` command with exact JSON payloads, expected values enumerated in tables, and defined placeholders (<root>, <test-start-ms>) — copy-paste ready and covering all common cases, matching anchor 5.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with an explicit assertion after every command, hard failure gates ("If the server fails to start within 60 seconds, report FAIL for all suites and skip to Step 5"), a bounded retry feedback loop in Recovery ("Only give up after one retry attempt per suite"), and a required summary table — matching anchor 5's validation-and-recovery standard.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so all content lives in one ~320-line SKILL.md. Section structure is clean and navigable (numbered steps, per-suite headers, tables, Recovery, Known Issues), fitting anchor 4's "good structure; most content appropriately placed" — but there is no layering at all (expected-value tables and known issues are fully inline), so it falls short of anchor 5's well-signaled one-level-deep references.

4 / 5

Total

18

/

20

Passed

Description

70%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 specific and highly distinctive within its niche, naming the exact components, fixture, and CLI tool involved. Its main weakness is the complete absence of "when to use" trigger guidance, which caps completeness at 3 and limits natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g., "Use when verifying DomeGradient/IBLGradient behavior, after changes to environment or lighting components, or when asked to run the poke environment tests."

Include natural trigger variations users might say, such as "environment test", "scene background", "image-based lighting", or "run poke tests", so the description matches anchor-5 trigger coverage.

Consider briefly naming the breadth of test coverage (system registration, component schemas, scene hierarchy, ECS modification, stability) so the "what" is comprehensive rather than partial.

DimensionReasoningScore

Specificity

The description names concrete objects and actions — "authored DomeGradient and IBLGradient, component schemas", "against the poke example using the iwsdk CLI" — but omits most of the skill's actual coverage (system registration, scene hierarchy, ECS modification, stability), so it is not comprehensive. It lists several specific actions rather than only 1-2, placing it above anchor 3.

4 / 5

Completeness

The "what" is clear (test the authored environment system against the poke example with the iwsdk CLI), but there is no "Use when..." clause or any equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. It cannot score 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"DomeGradient", "IBLGradient", "poke", and "iwsdk CLI" are the natural terms a user in this domain would say, giving good keyword coverage. It falls short of anchor 5 because no synonyms or common variations appear (e.g., "environment tests", "run poke tests", "scene background", "image-based lighting").

4 / 5

Distinctiveness Conflict Risk

The exact component names (DomeGradient, IBLGradient), fixture name (poke), and tool name (iwsdk CLI) define a clear niche with distinct triggers, making it very unlikely to fire for the wrong skill. It matches anchor 5 cleanly.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.