CtrlK
BlogDocsLog inGet started
Tessl Logo

test-environment

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

61

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/test-environment/SKILL.md
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 highly actionable, well-sequenced test procedure with strong validation and recovery guidance, limited only by minor redundancy and the lack of any external reference split. It is near-exemplary for an operational test skill.

DimensionReasoningScore

Conciseness

The body is dense and almost every line is a concrete command, assertion, or expected-value table that earns its place; the only trimming opportunity is the duplicated JSON-boolean warning (top IMPORTANT block and Known Issues), which keeps it just short of a 5.

4 / 5

Actionability

Every step gives copy-paste-ready `npx iwsdk` commands with exact `--input-json` payloads, explicit assertions, and expected-value tables, fully covering the common cases.

5 / 5

Workflow Clarity

A clear five-step sequence with explicit validation checkpoints ("Assert:", "Wait for this to complete before proceeding", skip-to-Step-5 fallbacks), a Recovery feedback loop, and a one-retry-per-suite policy — strong validation for a batch test operation.

5 / 5

Progressive Disclosure

Content is well-organized into Configuration, sequential Steps, six Suites, Recovery, and Known Issues with clear headers; with no bundle files present everything is inline, and the large expected-value tables could arguably live in references, which is the minor gap keeping it from a 5.

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 specific and clearly distinct but is missing explicit "when to use" trigger guidance, which limits its completeness and natural trigger-term coverage. Adding a "Use when..." clause naming the natural user phrasing would raise the weaker dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when verifying the IWSDK environment system or running gradient/IBL environment tests."

Include natural synonyms users might say ("run environment tests", "verify gradient lighting") alongside the component jargon.

Consider listing the suite variants from the argument-hint in the description so the scope of "test" is concrete.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action ("Test environment system ... against the poke example using the iwsdk CLI") plus the components under test (DomeGradient, IBLGradient), but it does not list several distinct actions, so it falls short of a 4.

3 / 5

Completeness

It has a clear "what" (test the authored environment system and component schemas against the poke example via the iwsdk CLI) but no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

"Test environment system" is a natural phrase the target user would say, and the component names are domain-relevant, but it lacks synonyms or variations (e.g. "run tests", "verify environment") and leans heavily on proper-noun jargon.

3 / 5

Distinctiveness Conflict Risk

The highly specific proper nouns (IWSDK, DomeGradient, IBLGradient, poke example) carve out a clear niche with minimal overlap risk against other skills.

5 / 5

Total

14

/

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.

Validation15 / 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
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.