iwsdk-debug
Debug continuous behavior in WebXR scenes — physics, animations, collisions, game loops, or any real-time interaction that happens too fast for an agent to observe. Uses ECS pause/step/snapshot/diff to freeze time and inspect state frame by frame.
73
91%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that clearly identifies a specific niche (debugging real-time WebXR behavior) with concrete actions and relevant trigger terms. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill over others. The technical specificity and natural keyword coverage are excellent.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to debug real-time or continuous behavior in WebXR scenes, mentions frame-by-frame debugging, or encounters issues with physics/animation/collision loops that are too fast to observe.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: debug continuous behavior, physics, animations, collisions, game loops, real-time interaction. Also specifies concrete techniques: ECS pause/step/snapshot/diff, freeze time, inspect state frame by frame. | 3 / 3 |
Completeness | Clearly answers 'what' (debug continuous behavior in WebXR scenes using ECS pause/step/snapshot/diff) but lacks an explicit 'Use when...' clause. The when is implied but not stated explicitly, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'WebXR', 'physics', 'animations', 'collisions', 'game loops', 'real-time', 'debug', 'ECS', 'frame by frame', 'pause', 'snapshot'. These are terms developers naturally use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: WebXR + continuous behavior debugging + ECS frame-by-frame inspection. This is unlikely to conflict with general debugging skills, general WebXR skills, or general animation skills due to its very specific combination of domain and technique. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently teaches a non-trivial debugging technique. It provides a clear, actionable core workflow with specific tool calls and parameters, domain-specific patterns with concrete field names to inspect, and important operational notes. The content is well-structured, concise, and assumes Claude's competence throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what physics, animations, or ECS are — it assumes Claude knows these concepts. Every section provides domain-specific, non-obvious guidance. The tool reference table is compact and informative. The patterns section uses terse, actionable bullet points. | 3 / 3 |
Actionability | The skill provides specific tool calls with exact parameter formats (e.g., `ecs_step({"count":N,"delta":0.016})`), concrete field names to inspect in diffs (e.g., `PhysicsBody._linearVelocity`), and specific diagnostic steps for each scenario. The core workflow is a numbered, executable sequence with exact tool invocations. | 3 / 3 |
Workflow Clarity | The core workflow is a clear 10-step sequence with explicit validation checkpoints (screenshot to visually verify, diff to inspect changes). It includes a feedback loop (repeat steps 5-8), a critical ordering insight (pause BEFORE triggering), and the system isolation pattern provides a clear diagnostic loop (toggle system, step, observe, conclude). | 3 / 3 |
Progressive Disclosure | For a standalone skill with no bundle files, the content is well-organized with clear sections: core workflow first, then tool reference table, stepping guidelines, domain-specific patterns, and notes. The structure progresses from general to specific without being monolithic, and each section is clearly delineated and scannable. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- facebook/immersive-web-sdk
- Commit
3a08b40
- 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.