CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

iwsdk-debug

Diagnose and verify real-time IWSDK behavior with bounded ECS pause, query, snapshot, step, and diff loops. Use for physics, animation, collision, interaction, or state bugs that cannot be proven from a screenshot.

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured, restrained debugging workflow with concrete tool invocations and explicit validation via ECS diffs and a bounded replay. Minor gaps are the unshown entity-query syntax and slight redundancy among the scope-limiting prohibitions.

DimensionReasoningScore

Conciseness

The body is dense and IWSDK-specific with no explanation of concepts Claude already knows, but the repeated do-not-inspect/do-not-read-payload cautions across sections 2 and 3 could be consolidated for a fully lean result.

4 / 5

Actionability

Concrete tool calls (ecs_pause, ecs_snapshot with labels, ecs_step at 0.016, ecs_diff, ecs_resume), a copy-ready CLI command (npx @iwsdk/cli browser screenshot --output-file <path>), and specific component JSON forms make the guidance mostly executable, though the entity-query syntax referenced in section 1 is never shown.

4 / 5

Workflow Clarity

The probe sequence is explicitly numbered (pause, snapshot, step, snapshot, diff), validation is built in via the labeled diff and post-build replay with identical labels and timestep, and an explicit stop condition plus a one-correction bound provide clear feedback loops.

5 / 5

Progressive Disclosure

With no bundle files, the ~65-line body is self-contained and cleanly sectioned; it sits just outside the under-50-line simple-skill case but is well organized with nothing that clearly belongs in a separate file.

4 / 5

Total

17

/

20

Passed

Description

88%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 that clearly states capabilities and explicit trigger conditions in third person with no filler. The only weaknesses are absent trigger synonyms and a when-clause that could fire for non-IWSDK physics/animation bugs.

DimensionReasoningScore

Specificity

"Diagnose and verify real-time IWSDK behavior with bounded ECS pause, query, snapshot, step, and diff loops" names the domain and five concrete operations with comprehensive coverage, matching the top anchor rather than the minor-gaps level.

5 / 5

Completeness

It explicitly answers both what ("Diagnose and verify real-time IWSDK behavior with bounded ECS...loops") and when ("Use for physics, animation, collision, interaction, or state bugs that cannot be proven from a screenshot") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use for physics, animation, collision, interaction, or state bugs" provides good natural keyword coverage, but common variations users might say (e.g., "glitch", "jitter", "clipping") are missing, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The IWSDK/ECS runtime niche is distinct, but the when-clause ("physics, animation, collision... bugs") is not bound to IWSDK projects, so generic engine-debugging requests carry minor overlap risk.

4 / 5

Total

18

/

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