CtrlK
BlogDocsLog inGet started
Tessl Logo

test-level

Test level system (LevelRoot, LevelTag, authored environment, scene hierarchy) against the poke example using the iwsdk CLI.

63

Quality

75%

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-level/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 highly actionable with executable commands, explicit assertions, and a well-sequenced workflow including validation and recovery loops. Minor gains available from trimming explanatory prose and moving known-issues reference material into a separate file.

DimensionReasoningScore

Conciseness

Mostly lean with concrete commands and assertions, but a few explanatory passages about CLI auto-discovery and LevelSystem internals could be trimmed; not fully token-optimal.

4 / 5

Actionability

Every suite ships copy-paste-ready npx iwsdk commands with exact --input-json payloads and precise assertions (entity counts, component lists, expected values), covering common cases plus recovery.

5 / 5

Workflow Clarity

Clear five-step sequence with explicit validation checkpoints (connectivity, pre-test logs, per-suite assertions), a failure short-circuit, and a retry feedback loop for transient errors.

5 / 5

Progressive Disclosure

Well-organized into steps, suites, recovery, and known-issues sections with clear headers, but all reference-style content is inlined monolithically with no one-level-deep external references despite exceeding 50 lines.

4 / 5

Total

18

/

20

Passed

Description

62%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 lacks an explicit 'when to use' trigger clause and relies on technical jargon over natural user phrasing. Adding a 'Use when...' sentence with common trigger terms would lift completeness and trigger-term quality.

Suggestions

Append a 'Use when ...' clause (e.g., 'Use when verifying the IWSDK level system or running level/scene regression tests').

Add natural trigger synonyms users might say, such as 'level system tests', 'scene hierarchy checks', or 'XR level regression'.

Reframe the listed components as concrete actions (e.g., 'Verify LevelRoot identity, check LevelTag membership, validate authored environment') to move specificity toward 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete subjects (LevelRoot, LevelTag, authored environment, scene hierarchy) plus the target example and CLI, but frames them as objects of a single 'Test' action rather than multiple distinct actions, so it sits just below the comprehensive 5 anchor.

4 / 5

Completeness

Clearly states what the skill does but provides no 'Use when...' trigger guidance, capping completeness at 3 per the missing-trigger-clause rule.

3 / 5

Trigger Term Quality

Includes the natural phrase 'Test level system' but leans heavily on SDK jargon (LevelRoot, LevelTag, iwsdk CLI) and omits common synonyms or variations a user might say.

3 / 5

Distinctiveness Conflict Risk

Targets a narrow, specific niche (testing the iwsdk level system against the poke example) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

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.