arcgis-widgets-ui
Build map user interfaces with ArcGIS widgets, Map Components, and Calcite Design System. Use for adding legends, layer lists, search, tables, time sliders, and custom UI layouts.
88
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly identifies its domain (ArcGIS map UI development), lists specific capabilities and components, and provides explicit trigger guidance via the 'Use for...' clause. The description is concise, uses third-person voice, and includes enough domain-specific terminology to be both discoverable and distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and components: 'ArcGIS widgets, Map Components, Calcite Design System' and specific features like 'legends, layer lists, search, tables, time sliders, and custom UI layouts.' | 3 / 3 |
Completeness | Clearly answers both what ('Build map user interfaces with ArcGIS widgets, Map Components, and Calcite Design System') and when ('Use for adding legends, layer lists, search, tables, time sliders, and custom UI layouts'). The 'Use for...' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'map', 'ArcGIS', 'widgets', 'Calcite', 'legend', 'layer list', 'search', 'table', 'time slider', 'UI layouts'. These cover the terms a developer working with ArcGIS mapping would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around ArcGIS, Calcite Design System, and specific map UI components. Unlikely to conflict with generic UI or web development skills due to the domain-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, well-organized reference skill for ArcGIS widgets and UI development. Its greatest strength is actionability—nearly every concept is backed by executable code showing both Map Component and Core API approaches. The main weakness is that the massive component reference table and extensive inline examples make it quite long, and some content could be offloaded to referenced files to improve token efficiency.
Suggestions
Move the 50+ row Map Components Overview table to a separate reference file (e.g., COMPONENTS.md) and keep only the most common 10-15 components inline.
Add a brief decision flowchart or criteria list for when to use Map Components vs Core API widgets vs Calcite layout, to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient but includes an exhaustive component reference table (50+ rows) that could be split into a separate file. Some sections like the full Calcite layout example are verbose. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Excellent actionability with fully executable HTML and JavaScript code examples throughout. Import patterns, slot-based positioning, widget configuration, event handling, and Calcite integration all have copy-paste ready code with both Map Component and Core API approaches shown. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/catalog rather than a multi-step workflow, so explicit sequencing is less critical. However, there's no clear guidance on the decision process for choosing between Map Components vs Core API approaches, and the Common Pitfalls section serves as implicit validation but lacks explicit verification steps. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from imports to components to layouts to pitfalls. References to related skills (arcgis-widgets-advanced, arcgis-map-tools, arcgis-editing, arcgis-tables-forms) are clearly signaled at the end, keeping this file focused on core widget/UI patterns with one-level-deep navigation. | 3 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (571 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Commit
d84407b
- 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.