CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./contexts/4.34/skills/arcgis-layers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Scale 1-3

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 code examples covering a wide range of layer types. Its main weakness is length — it reads more like comprehensive API documentation than a lean skill, and some less common layer types could be moved to a separate reference file. The workflow clarity could be improved with explicit multi-step sequences for common tasks like 'add layer → wait for load → query features → handle results'.

Suggestions

Consider moving less common layer types (MapNotesLayer, GeoRSSLayer, ParquetLayer, StreamLayer, WebTileLayer) to a separate reference file to reduce the main skill's token footprint.

Add a 'Common Workflow' section with a numbered sequence showing the typical add-layer-to-query-results pipeline with explicit validation/error-handling checkpoints (e.g., check layer.loadStatus, handle query errors).

DimensionReasoningScore

Conciseness

The skill is comprehensive but quite long (~400+ lines). The layer type overview table is efficient, but the sheer volume of layer examples (MapNotesLayer, GeoRSSLayer, ParquetLayer, etc.) makes this feel like a reference manual rather than a lean skill. Some sections like the Common Pitfalls with anti-pattern/correct pairs are valuable but verbose. The inline comments explaining obvious things (e.g., '// Array of Graphic objects', '// Column name for lat') add minor bloat.

2 / 3

Actionability

Excellent actionability throughout. Every layer type has fully executable JavaScript code with proper imports, constructor configurations, and method calls. The querying section covers basic, spatial, pagination, statistics, and client-side queries with copy-paste ready code. The Common Pitfalls section provides both anti-patterns and correct patterns with concrete examples.

3 / 3

Workflow Clarity

The skill covers individual operations well but lacks explicit multi-step workflow sequences. The Layer Loading section hints at a workflow (load → access metadata → use layerView) but doesn't present it as a clear numbered sequence with validation checkpoints. For operations like querying features after adding layers, there's no explicit workflow showing the full sequence with error handling or validation steps.

2 / 3

Progressive Disclosure

Good progressive disclosure with a clear overview table at the top, well-organized sections by layer type, and appropriate references to external skills ('See arcgis-advanced-layers for WMS, WFS, KML...' and 'See arcgis-core-maps skill for autocasting guidance'). Reference samples are listed at the end. The structure flows logically from common layers to specialized layers to management to querying.

3 / 3

Total

10

/

12

Passed

Description

72%Scale 1-3

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 is reasonably strong with good domain-specific trigger terms and clear distinctiveness for ArcGIS layer management. Its main weaknesses are the somewhat generic action verbs ('add', 'manage', 'configuration') and the lack of an explicit 'Use when...' clause that would help Claude know exactly when to select this skill over others.

Suggestions

Replace generic verbs with more specific actions, e.g., 'Add, configure, query, filter, style, and remove data layers in ArcGIS maps'.

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about adding layers to a map, querying layer features, configuring layer properties, or working with ArcGIS layer types.'

DimensionReasoningScore

Specificity

Names the domain (ArcGIS maps, data layers) and lists specific layer types (FeatureLayer, TileLayer, SceneLayer, GeoJSONLayer), but the actions are somewhat generic ('add', 'manage', 'configuration', 'queries', 'management') rather than listing multiple concrete operations.

2 / 3

Completeness

Clearly answers 'what' (add and manage data layers in ArcGIS maps) and provides some trigger context ('Use for FeatureLayer, TileLayer...'), but lacks an explicit 'Use when...' clause describing when Claude should select this skill. The 'Use for' partially serves this purpose but doesn't fully articulate trigger conditions.

2 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'FeatureLayer', 'TileLayer', 'SceneLayer', 'GeoJSONLayer', 'data layers', 'ArcGIS', 'layer configuration', 'queries'. These are terms a developer working with ArcGIS would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: ArcGIS map layers specifically. The enumeration of specific layer types (FeatureLayer, TileLayer, SceneLayer, GeoJSONLayer) makes it very unlikely to conflict with other skills.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (655 lines); consider splitting into references/ and linking

Warning

Total

10

/

11

Passed

Repository
SaschaBrunnerCH/arcgis-maps-sdk-js-ai-context
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.