iwsdk-ui-panel
Develop and iterate on IWSDK UI panels efficiently. Use when working on PanelUI components, debugging UI layout, or improving UI design in IWSDK applications.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/iwsdk-ui-panel/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is reasonably well-structured with a clear 'Use when' clause and a distinct niche (IWSDK PanelUI). However, it lacks specificity in the concrete actions it performs—'develop and iterate' is vague—and could benefit from listing more specific capabilities and natural trigger terms users might use.
Suggestions
Add more concrete actions such as 'create panel layouts, configure panel properties, handle panel events, style panel components' to improve specificity.
Expand trigger terms with common variations users might say, such as 'panel widget', 'IWSDK dashboard', 'panel rendering', or specific file/component names associated with PanelUI.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (IWSDK UI panels, PanelUI components) and some actions ('develop', 'iterate', 'debugging UI layout', 'improving UI design'), but doesn't list multiple concrete specific actions like extracting, filling, merging, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (develop and iterate on IWSDK UI panels) and 'when' (explicit 'Use when' clause covering PanelUI components, debugging UI layout, or improving UI design in IWSDK applications). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'PanelUI', 'IWSDK', 'UI panels', 'UI layout', 'UI design', but these are fairly domain-specific and may miss common variations users might say. Terms like 'panel', 'widget', or specific component names are absent. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to IWSDK PanelUI components, which is a specific enough niche that it's unlikely to conflict with general UI or other framework-specific skills. | 3 / 3 |
Total | 10 / 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 solid, actionable skill with clear workflow steps and executable code examples for IWSDK UI panel development. Its main weakness is moderate verbosity—some explanatory text and basic CSS concepts could be trimmed to respect Claude's existing knowledge. The content would benefit from slightly tighter prose and potentially splitting reference material into separate files.
Suggestions
Remove explanatory prose that Claude already knows (e.g., what flexbox does, the introductory sentence 'This skill teaches...', and the 'Why close?' explanation could be shortened to a brief inline comment).
Consider extracting the ScreenSpace Component Reference and UIKit Size Signals sections into separate reference files to improve progressive disclosure and reduce the main file length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., 'This skill teaches the efficient workflow...', explaining why the camera should be close, explaining what flexbox does). Some sections like 'Common Workflow Tips' with basic CSS concepts add little value for Claude. However, the code examples are reasonably focused and most content is relevant. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code snippets throughout, with concrete values, specific component configurations, and copy-paste ready examples. The complete development setup example at the end ties everything together into a runnable setup. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps (1-5), each step has a clear purpose and concrete implementation. The cleanup checklist before production serves as a validation checkpoint. The troubleshooting section provides error recovery guidance. The workflow is well-structured for a development iteration cycle. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but it's a fairly long monolithic document (~180 lines of content). The ScreenSpace reference, UIKit size signals debugging, and common workflow tips could potentially be split into separate reference files. However, with no bundle files provided, the inline approach is acceptable though not optimal. | 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | 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.