iwsdk-ui
Develop and iterate on IWSDK PanelUI components. Use when the user wants to create, modify, debug, or improve UI panels in their IWSDK application. Covers UIKITML editing, full-screen preview with ScreenSpace, and visual verification.
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
85%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 well-crafted skill description that clearly defines its niche within IWSDK PanelUI development. It provides explicit 'what' and 'when' guidance, lists concrete actions, and uses highly distinctive domain-specific terminology that minimizes conflict risk. The only minor weakness is that the trigger terms are quite technical, which is appropriate given the specialized domain but could miss some natural user phrasings.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create, modify, debug, or improve UI panels', 'UIKITML editing', 'full-screen preview with ScreenSpace', and 'visual verification'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (develop and iterate on IWSDK PanelUI components, UIKITML editing, full-screen preview, visual verification) and 'when' (explicit 'Use when the user wants to create, modify, debug, or improve UI panels in their IWSDK application'). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'PanelUI', 'IWSDK', 'UI panels', 'UIKITML', 'ScreenSpace', but these are domain-specific/technical terms. Natural user terms like 'panel', 'UI', 'preview' are present but could include more variations. The terms are fairly niche and technical. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with very specific domain terms: 'IWSDK', 'PanelUI', 'UIKITML', 'ScreenSpace'. These are unique enough that this skill is unlikely to conflict with generic UI or web development skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill that provides a clear workflow for IWSDK PanelUI development with good validation checkpoints. Its main strengths are the concrete tool calls, executable code examples, and the explicit edit-verify-cleanup cycle. Minor weaknesses include some verbosity in explanations and the Notes section containing supplementary information that could be better organized or separated.
Suggestions
Tighten the Notes section by removing information Claude can infer (e.g., the VR behavior note is tangential to the core workflow) or move it to a separate reference file.
Reduce conditional verbosity in Step 2 by using a more compact format for the 'already has ScreenSpace' vs 'does not have ScreenSpace' branching.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and domain-specific, but includes some unnecessary explanation (e.g., explaining what ScreenSpace does conceptually, the VR behavior note, and some verbose conditional branching that could be tightened). It generally respects Claude's intelligence but could be leaner. | 2 / 3 |
Actionability | Provides concrete, executable TypeScript code snippets, specific tool calls (ecs_find_entities, ecs_query_entity, browser_screenshot, mcp__iwsdk-reference__search_code), and clear instructions for each step. The guidance is specific and directly usable. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (identify → setup preview → verify → edit with iteration loop → cleanup) with explicit validation checkpoints (browser_screenshot after setup, after each edit, and after cleanup). The edit-screenshot feedback loop is well-defined, and the cleanup step includes state restoration with verification. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but everything is inline in a single file. The Notes section at the end contains supplementary information that could potentially be separated. No bundle files are provided, so there are no external references, but the skill is moderately long (~80 lines of content) and some reference material (UIKITML details, ScreenSpace behavior) could be split out. | 2 / 3 |
Total | 10 / 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.