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-structured skill description that clearly communicates both what the skill does and when to use it, with a strong explicit 'Use when' clause. The domain-specific terminology (IWSDK, PanelUI, UIKITML) makes it highly distinctive but may limit trigger term coverage for users who describe their needs in more general UI development terms. Overall, it's a solid description that would perform well in skill selection.
Suggestions
Consider adding broader natural language trigger terms like 'user interface', 'panel layout', or 'UI components' to catch users who may not use the exact IWSDK terminology in their requests.
| 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 domain-specific terms like 'IWSDK', 'PanelUI', 'UIKITML', 'ScreenSpace' which are relevant but highly technical. Natural user terms like 'UI panels', 'create', 'modify', 'debug' are present, but common variations or broader terms users might say (e.g., 'user interface', 'panel layout', 'UI components') are missing. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific technology stack (IWSDK, PanelUI, UIKITML, ScreenSpace). Very unlikely to conflict with other skills given the niche domain-specific terminology. | 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 for IWSDK PanelUI development with clear workflow steps and validation checkpoints. Its main strengths are concrete tool calls, explicit verification steps at each stage, and proper cleanup requirements. Minor weaknesses include some slightly verbose explanations and all content being in a single file when some reference material (UIKITML key facts, Notes) could be separated.
Suggestions
Tighten the introductory sentence and remove phrases like 'This is where the user's request drives the work' that don't add actionable value.
Consider moving the 'Key facts about UIKITML' and 'Notes' sections into a separate reference file to keep the main skill focused on the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation (e.g., 'This is where the user's request drives the work', explaining what ScreenSpace does conceptually). Some sections could be tightened, but most content earns its place with domain-specific knowledge Claude wouldn't have. | 2 / 3 |
Actionability | Provides concrete TypeScript code for ScreenSpace setup, specific MCP tool calls (ecs_find_entities, ecs_query_entity, browser_screenshot, mcp__iwsdk-reference__search_code), exact file paths, and clear commands. The guidance is specific and executable throughout. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow with explicit validation checkpoints: screenshot after setup (Step 3), screenshot after each edit (Verify changes), and screenshot after cleanup. Includes a feedback loop (edit-screenshot cycle) and explicit restore/cleanup requirements. The sequence is well-defined with numbered steps. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections (Required Core, UI Editing, Cleanup, Notes), but all content is inline in a single file. The Notes section at the end contains useful but somewhat lengthy supplementary information that could potentially be separated. No bundle files are provided, so there's no external reference structure, but the skill is moderately long (~90 lines) and could benefit from splitting the UIKITML reference details. | 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
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.