CtrlK
BlogDocsLog inGet started
Tessl Logo

test-ui

Test UIKitML asset and ScreenSpace UI behavior against the poke example using the iwsdk CLI.

64

Quality

76%

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-ui/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 well-structured, fully executable test procedure with strong validation checkpoints and recovery guidance. Its only weak spot is progressive disclosure — everything is inline with no reference files for background material.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — concrete commands and assertions with no concept over-explanation — but repeats the dev-server start command in Recovery and could be trimmed slightly, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Every test provides fully executable, copy-paste-ready commands such as 'npx iwsdk ecs find --input-json {"withComponents":["ScreenSpace"]}' with explicit JSON payloads and precise assertions, matching 'fully executable; copy-paste ready'.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit 'Assert' validation checkpoints, a Recovery feedback loop (stop → restart → re-run → retry once), and a results summary table, matching 'clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

No bundle files exist so all content is inline, but it is well-sectioned into Steps, Suites, Recovery, and Known Issues; the only gap is that the reference-like Known Issues section could live in a separate file, fitting 'good structure; minor organization gaps'.

4 / 5

Total

18

/

20

Passed

Description

65%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, naming concrete domain artifacts and the CLI used. Its main weakness is the absence of any 'Use when…' trigger guidance, leaving the 'when' implicit.

Suggestions

Append an explicit 'Use when…' trigger clause, e.g. 'Use when verifying the poke example's UIKitML and ScreenSpace UI after changes to the UI system.'

Expand the single 'Test' verb into a couple of concrete actions (e.g. 'verify panel loading, ScreenSpace values, and system registration') to lift specificity.

Add common user-facing synonyms or the suite names so the trigger terms cover more variations users might say.

DimensionReasoningScore

Specificity

Quotes 'Test UIKitML asset and ScreenSpace UI behavior against the poke example using the iwsdk CLI' — names the domain and one concrete action, but offers only a single verb rather than several specific actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It clearly states the 'what' ('Test UIKitML asset and ScreenSpace UI behavior') but provides no 'Use when…' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Terms like 'UIKitML', 'ScreenSpace UI', 'poke example', and 'iwsdk CLI' are exactly the niche-natural phrases a user of this system would say, giving good keyword coverage with only minor synonyms missing.

4 / 5

Distinctiveness Conflict Risk

The reference to 'UIKitML', 'ScreenSpace UI', 'poke example', and 'iwsdk CLI' carves out a clear niche with distinct triggers and minimal risk of conflicting 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.