CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

iwsdk-depth-occlusion

Add or repair IWSDK WebXR depth sensing and real-world occlusion in AR. Use for DepthSensingSystem, DepthOccludable, occlusion modes, or passthrough depth troubleshooting.

Quality

90%

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

The canonical home for this skill is iwsdk-depth-occlusion in facebook/immersive-web-sdk

SKILL.md
Quality
Evals
Security

Quality

Content

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

An excellent instruction-only skill body: dense, executable, and verification-first, with concrete correction loops and explicit stop conditions. The only structural note is that it is a single flat file slightly over the simple-skill size with no progressive disclosure layer, which is acceptable given its density.

DimensionReasoningScore

Conciseness

The body is lean and purely operational — exact JSON/TS snippets, exact scene payload values, and CLI commands with no concept explanations; the negative guardrails ("do not call scene capabilities, CLI --help, inspect node_modules") are operational constraints, not padding, so every token earns its place.

5 / 5

Actionability

Guidance is fully executable: copy-paste-ready depthSensing config, registerSystem code, exact occlusion mode payloads ("{}", "{ \"mode\": \"HardOcclusion\" }"), and seven exact `npx @iwsdk/cli` commands including argument JSON formats.

5 / 5

Workflow Clarity

The Implement section gives a numbered sequence and the Verify section provides explicit validation checkpoints (console warning check, entity/system queries, live screenshot) plus a bounded feedback loop ("Make one focused correction if the measured runtime disagrees, then stop").

5 / 5

Progressive Disclosure

The content is self-contained with clear section structure and deliberately avoids unnecessary reference loads, but at ~82 lines it exceeds the under-50-line simple-skill exception and offers no well-signaled reference structure, so it fits the good-structure anchor rather than the top one.

4 / 5

Total

19

/

20

Passed

Description

82%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 with an explicit trigger clause, precise domain framing, and low conflict risk. Its only weakness is that the action list is brief (add/repair/troubleshoot) rather than a fuller enumeration of capabilities.

DimensionReasoningScore

Specificity

"Add or repair IWSDK WebXR depth sensing and real-world occlusion in AR" names a specific domain with two concrete actions (add, repair) plus troubleshooting, but does not enumerate several distinct actions, matching the 1-2-concrete-actions anchor rather than the comprehensive one.

3 / 5

Completeness

It clearly answers both what ("Add or repair IWSDK WebXR depth sensing and real-world occlusion in AR") and when ("Use for DepthSensingSystem, DepthOccludable, occlusion modes, or passthrough depth troubleshooting") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Use for DepthSensingSystem, DepthOccludable, occlusion modes, or passthrough depth troubleshooting" includes strong natural keywords (exact component names, occlusion modes, passthrough depth), but misses a few common variations such as "depth occlusion" or "AR occlusion".

4 / 5

Distinctiveness Conflict Risk

The IWSDK/WebXR depth-occlusion niche is highly specific with distinct trigger terms (DepthSensingSystem, DepthOccludable, passthrough depth), making conflict with other skills minimal.

5 / 5

Total

17

/

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

packages/core/agent-guidance/claude/.claude/skills/iwsdk-depth-occlusion/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.