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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable workflow with executable code and a clear iteration sequence including screenshot verification. It loses points for some redundant/basic explanation and for keeping reference-style material inline in one large file instead of splitting it into bundled references.

Suggestions

Trim explanations of concepts Claude already knows (e.g. the inline flexbox centering comments) and de-duplicate the ScreenSpace example that appears in three sections.

Move the ScreenSpace Component Reference and Troubleshooting sections into separate reference files (e.g. references/SCREENSPACE.md, references/TROUBLESHOOTING.md) and link to them one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and dominated by useful IWSDK-specific code, but it includes explanation Claude already knows (e.g. annotated flexbox centering with 'Stack vertically'/'Center vertically' comments) and repeats the ScreenSpace example across Quick Iteration, Reference, and Complete Setup sections, so it could be tightened.	2 / 3
Actionability	Provides complete, executable TypeScript snippets (ScreenSpace add, backdrop mesh, camera positioning, size-signal logging) plus copy-paste-ready CSS tips, all concrete rather than pseudocode.	3 / 3
Workflow Clarity	The Quick Iteration Workflow lays out a clear numbered 5-step sequence with an explicit screenshot-based verification/feedback loop in step 4 and a separate pre-production cleanup checklist, satisfying the validation-checkpoint expectation.	3 / 3
Progressive Disclosure	It is a single monolithic file well-organized into sections but over 50 lines with no bundle references; content like the ScreenSpace Component Reference and Troubleshooting could live in separate one-level-deep reference files rather than inline.	2 / 3
	Total	10 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description that clearly states both capability and an explicit trigger clause scoped to the IWSDK UI domain. Its only weakness is that the capability list is light on concrete enumerated actions.

Dimension	Reasoning	Score
Specificity	Names the domain (IWSDK UI panels) and two actions ('Develop and iterate'), but does not enumerate multiple concrete operations the way a 3-anchor description like 'extract, fill, merge' does.	2 / 3
Completeness	It explicitly answers both 'what' ('Develop and iterate on IWSDK UI panels efficiently') and 'when' via an explicit 'Use when ...' clause, matching the 3-anchor pattern.	3 / 3
Trigger Term Quality	The trigger clause surfaces natural terms a user in this domain would say — 'PanelUI components', 'debugging UI layout', 'improving UI design', 'IWSDK applications' — with good coverage of phrasings.	3 / 3
Distinctiveness Conflict Risk	The IWSDK/PanelUI niche and its specific triggers are unlikely to fire for unrelated skills, giving it a clear distinct niche.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: facebook/immersive-web-sdk
Commit: 42af866

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.