arcgis-layers
Add and manage data layers in ArcGIS maps. Use for FeatureLayer, TileLayer, SceneLayer, GeoJSONLayer, and all other layer types. Covers layer configuration, queries, and management.
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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 solid skill description that clearly identifies its domain (ArcGIS map layers) and provides good trigger terms through specific layer type names. The main weakness is that the capability descriptions are somewhat general ('configuration, queries, and management') rather than listing concrete specific actions. The 'Use for...' clause effectively serves as trigger guidance.
Suggestions
Replace generic terms like 'configuration' and 'management' with more specific actions such as 'set renderers, apply filters, define popups, configure labeling, handle layer visibility and ordering'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ArcGIS maps) and some actions ('add and manage data layers', 'layer configuration, queries, and management'), but the actions are somewhat general rather than listing multiple concrete operations like 'filter features by attribute', 'set renderer styles', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (add and manage data layers, layer configuration, queries, and management) and 'when' ('Use for FeatureLayer, TileLayer, SceneLayer, GeoJSONLayer, and all other layer types'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'FeatureLayer', 'TileLayer', 'SceneLayer', 'GeoJSONLayer', 'ArcGIS', 'data layers', 'layer configuration', 'queries'. These cover specific layer type names users would mention when working with ArcGIS. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to ArcGIS layer management with distinct trigger terms like specific layer type names (FeatureLayer, TileLayer, SceneLayer, GeoJSONLayer). Unlikely to conflict with other skills unless there are multiple ArcGIS-related skills. | 3 / 3 |
Total | 11 / 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 well-structured, highly actionable reference skill for ArcGIS layers with excellent progressive disclosure and concrete code examples throughout. Its main weaknesses are verbosity (the sheer volume of layer type examples could be trimmed or split into referenced files) and the lack of explicit validation/error-handling workflows when performing layer operations. The Common Pitfalls section is a strong addition that addresses real developer pain points with before/after code patterns.
Suggestions
Consider moving less common layer types (GeoRSSLayer, MapNotesLayer, WebTileLayer, ParquetLayer) to a separate referenced file to reduce the main skill's token footprint.
Add brief error handling patterns or validation checkpoints to the querying and layer loading sections (e.g., try/catch around queryFeatures, checking layer.loadStatus before proceeding).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but quite long (~450+ lines). The layer types overview table and many of the simpler layer examples (TileLayer, VectorTileLayer, GeoRSSLayer, MapNotesLayer) could be trimmed or moved to a referenced file. The Common Pitfalls section is thorough but includes both anti-pattern and correct pattern for each, which adds bulk. However, it avoids explaining basic concepts Claude would know. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready code examples with real import statements, constructor configurations, and method calls. The query examples, layer management operations, and common pitfalls all include concrete, runnable JavaScript/TypeScript code with realistic URLs and data. | 3 / 3 |
Workflow Clarity | Layer management steps (add, remove, reorder) are clear, and the query workflow is well-sequenced. However, there are no explicit validation checkpoints - for example, no guidance on verifying a layer loaded successfully before querying, or error handling patterns for failed queries. The pitfalls section partially compensates by showing load-before-access patterns, but these aren't integrated into a clear workflow with feedback loops. | 2 / 3 |
Progressive Disclosure | The skill has a clear overview table, well-organized sections by layer type, and appropriately delegates advanced topics to related skills (arcgis-advanced-layers, arcgis-visualization, arcgis-popup-templates, etc.). References are one level deep and clearly signaled with 'See' links. The specialized layers section explicitly points to arcgis-advanced-layers for WMS/WFS/KML. | 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 (708 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.