CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

iwsdk-ui

Build or modify manifest-backed IWSDK UIKitML with bounded preview, placement, and runtime verification. Use for spatial panels, browser HUDs, UIKitML layout, fonts, editor previews, and runtime element behavior.

Quality

87%

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

85%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.

A dense, highly actionable skill body: executable code, exact CLI forms, and a well-sequenced verification loop with explicit validation gates. The main weakness is structure: everything lives inline in one long SKILL.md with no reference files, and a few guardrail rules are repeated.

Suggestions

Move the deep-dive material (material-array emissive cloning, the XR poke/select verification command catalog, the Windows PowerShell contact-sheet script) into references/ files and link them one level deep from SKILL.md.

State the image-open budget once as a single policy in the verification section instead of repeating it across 'Fast path' and 'Verify with a bounded loop'.

Consolidate the repeated anti-discovery warnings ('do not call --help', 'do not inspect node_modules') into one place near the verification commands.

DimensionReasoningScore

Conciseness

Nearly every line is non-obvious, SDK-specific hard-won guidance (icon bundling limits, poke contactMs < 800 threshold, camera-facing rules) with no padding of concepts Claude already knows. Not 5 because the image-open budget is stated three times ("do not open any PNG, JPEG, or WebP", "artifacts/ui-runtime-review.jpg is the only image file to open", "do not open those files in model context") and several "do not call --help / do not inspect node_modules" warnings repeat.

4 / 5

Actionability

Fully executable throughout: copy-paste TypeScript snippets (requireElementById, createSystem, material cloning), exact npx @iwsdk/cli commands with JSON arguments, and a complete PowerShell contact-sheet command covering the common verification cases.

5 / 5

Workflow Clarity

Clear sequence (classify surface -> fast-path inspection -> author first pass -> connect runtime -> bounded verify loop) with numbered verification steps, an explicit final-gate checklist ("The final visual check must confirm..."), and concrete feedback loops (rerun the press when contactMs >= 800, use CLI error output instead of --help).

5 / 5

Progressive Disclosure

Well-sectioned with headers, but the skill is a single ~325-line file with no references/, scripts/, or assets/ bundle; deep-dive content that belongs in separate one-level-deep files (material-array emissive cloning, the XR/browser verification command catalog, the PowerShell contact-sheet script) is inlined. Better organized than anchor 2, but inline bulk keeps it below 4.

3 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description: concrete capabilities in third person, an explicit "Use for" trigger clause with domain-natural terms, and a distinct niche that is unlikely to fire for unrelated skills. Only minor room to broaden trigger synonyms (XR, immersive, scene).

DimensionReasoningScore

Specificity

"Build or modify manifest-backed IWSDK UIKitML with bounded preview, placement, and runtime verification" lists several concrete actions (build, modify, preview, placement, verification) plus specific artifact types (spatial panels, browser HUDs, fonts, editor previews). Not 5 because the coverage leans on SDK jargon rather than fully enumerated concrete actions; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

It explicitly answers both: what ("Build or modify manifest-backed IWSDK UIKitML with bounded preview, placement, and runtime verification") and when ("Use for spatial panels, browser HUDs, UIKitML layout, fonts, editor previews, and runtime element behavior") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"spatial panels, browser HUDs, UIKitML layout, fonts, editor previews, and runtime element behavior" are natural terms a user of this domain would say. Not 5 because common variations such as "XR", "immersive", or "scene" are missing; clearly above 3's "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

"IWSDK UIKitML" names a clear niche with distinct triggers (spatial panels, UIKitML layout, ScreenSpace-style HUDs); minimal conflict risk with any generic UI or document skill.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

facebook/immersive-web-sdk

Path

packages/create/guidance/claude/.claude/skills/iwsdk-ui/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.