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 well-structured with a clear 'Use when...' clause and targets a specific niche (IWSDK PanelUI), making it distinctive and complete. However, it could benefit from listing more concrete actions beyond 'develop and iterate' and including additional trigger terms that users might naturally use when requesting help with these components.
Suggestions
Add more specific concrete actions, e.g., 'Creates panel layouts, configures panel properties, handles panel events, styles PanelUI components' instead of the vague 'develop and iterate'.
Include additional natural trigger terms users might say, such as specific component names, file types, or common tasks like 'panel styling', 'panel configuration', or 'panel rendering issues'.
| 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 creating panels, styling components, handling events, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (develop and iterate on IWSDK UI panels) and 'when' with an explicit 'Use when...' clause covering three trigger scenarios: working on 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 project-specific terms. Missing common variations a user might say like 'panel layout', 'user interface', 'widget', or specific component names. | 2 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to IWSDK and PanelUI components, which creates a clear niche. It's unlikely to conflict with general UI skills or other framework-specific skills due to the distinct 'IWSDK' and 'PanelUI' identifiers. | 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 specific to IWSDK's PanelUI development. Its main weakness is verbosity—some explanations of basic concepts (flexbox, why cameras need to be close) and introductory framing could be trimmed. The content would also benefit from splitting reference material into separate files to keep the main skill lean.
Suggestions
Remove the introductory sentence ('This skill teaches...') and trim explanations of concepts Claude already knows (flexbox centering, basic CSS properties).
Move the 'ScreenSpace Component Reference', 'Understanding UIKit Size Signals', and 'Common Workflow Tips' sections into separate referenced files to keep the main SKILL.md focused on the core workflow.
| 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, and CSS concepts Claude already knows like flexbox centering). However, most content is reasonably focused on IWSDK-specific knowledge. Could be tightened by ~30%. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code snippets throughout, with concrete values, specific component APIs, and a complete end-to-end development setup example. Code is copy-paste ready with real imports and specific parameter values. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (5 numbered steps), includes a cleanup checklist before production, has a troubleshooting section for common issues, and the complete example ties everything together. The production cleanup step serves as a validation checkpoint for this non-destructive workflow. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's quite long (~180 lines) and could benefit from splitting the ScreenSpace reference, UIKit size signals debugging, and the complete example into separate referenced files. No bundle files exist to offload content to. | 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
b3d1162
- 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.