arcgis-widgets-advanced

Advanced and specialized widgets including BuildingExplorer, FloorFilter, Track, Locate, Histogram, ScaleBar, Compass, NavigationToggle, and media viewers

Quality

48%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./contexts/4.34/skills/arcgis-widgets-advanced/SKILL.md

Quality

Discovery

32%

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 lists specific widget names which provides some identification value, but it fails to explain what these widgets do, what framework they belong to, or when Claude should select this skill. It reads more like a category label than a functional description, and the absence of a 'Use when...' clause significantly limits its utility for skill selection.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about ArcGIS JS API widgets like building exploration, floor filtering, location tracking, scale bars, or compass navigation.'

Specify the framework/platform (e.g., ArcGIS JavaScript API) to improve distinctiveness and help Claude distinguish this from generic widget skills.

Describe concrete actions rather than just listing names, e.g., 'Implements and configures BuildingExplorer for 3D building visualization, FloorFilter for multi-story navigation, Track/Locate for geolocation...'

Dimension	Reasoning	Score
Specificity	The description names specific widgets (BuildingExplorer, FloorFilter, Track, Locate, Histogram, ScaleBar, Compass, NavigationToggle, media viewers), which provides some concrete detail, but it doesn't describe what actions can be performed with them—only that they exist as 'advanced and specialized widgets.'	2 / 3
Completeness	The description answers 'what' only partially (lists widget names without explaining capabilities) and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	The widget names themselves serve as trigger terms (e.g., 'BuildingExplorer', 'FloorFilter', 'ScaleBar', 'Compass'), and a user asking about these specific widgets would match. However, it lacks broader natural language terms users might say like 'map navigation', 'building floors', 'location tracking', or the framework name (likely ArcGIS).	2 / 3
Distinctiveness Conflict Risk	The specific widget names provide some distinctiveness, but 'advanced and specialized widgets' is vague and could overlap with other widget-related skills. Without naming the framework or platform, it's unclear what distinguishes these from widgets in other contexts.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

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 API reference for ArcGIS advanced widgets with excellent actionability — every widget has complete, executable examples in both component and core API forms. However, the content is overly long due to repetitive patterns across widgets, and would benefit from being restructured with a concise overview in SKILL.md pointing to per-widget detail files. The Common Pitfalls section adds genuine value but could be integrated into the relevant widget sections.

Suggestions

Reduce repetition by extracting per-widget detailed examples into separate reference files (e.g., BUILDING_EXPLORER.md, FLOOR_FILTER.md) and keep SKILL.md as a concise overview with the component table and one minimal example per widget.

Integrate validation/verification steps into Track and Locate sections (e.g., check for HTTPS, handle permission denial) rather than only listing pitfalls at the end.

Consolidate the three patterns shown for each widget (component, core API, external reference) into a single canonical example per widget in SKILL.md, with the alternate patterns in reference files.

Dimension	Reasoning	Score
Conciseness	The skill is quite long with repetitive patterns (component version, core API version, external reference version for each widget). Many examples follow identical structures that could be condensed. However, it doesn't waste tokens explaining basic concepts Claude already knows.	2 / 3
Actionability	All code examples are fully executable with proper imports, concrete URLs, and copy-paste ready patterns. Both the web component and core API approaches are shown with complete, working code including event handlers and configuration options.	3 / 3
Workflow Clarity	Individual widget usage is clear, but there are no explicit validation steps or error handling workflows. For widgets like Track that require HTTPS and permissions, the pitfalls section mentions requirements but doesn't integrate verification steps into the workflow. The combining section shows composition but lacks sequencing guidance.	2 / 3
Progressive Disclosure	The skill has good cross-references to related skills at the top and a reference samples section at the bottom. However, the content is monolithic — at ~500+ lines, the detailed examples for each widget could be split into separate reference files, with SKILL.md serving as an overview with the component table and basic examples only.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (778 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: SaschaBrunnerCH/arcgis-maps-sdk-js-ai-context
Commit: d84407b

Reviewed: 1 day 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.