CtrlK
BlogDocsLog inGet started
Tessl Logo

arcgis-advanced-layers

Work with advanced layer types including WMS, WFS, WMTS, OGCFeatureLayer, KMLLayer, MapImageLayer, CatalogLayer, and MediaLayer. Use for OGC services, server-side rendering, and georeferenced media content.

81

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-advanced-layers/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The description excels at trigger term coverage and distinctiveness by listing many specific layer type names that GIS developers would naturally reference. It also provides explicit 'Use for' guidance. Its main weakness is the vague 'Work with' opening—it would benefit from specifying concrete actions like configure, query, render, or add layers.

Suggestions

Replace 'Work with' with specific concrete actions such as 'Configure, query, and render advanced layer types' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (advanced layer types) and lists specific layer type names (WMS, WFS, WMTS, etc.), but doesn't describe concrete actions—it says 'Work with' which is vague about what operations are performed (add, configure, query, style?).

2 / 3

Completeness

Answers both 'what' (work with advanced layer types including specific named types) and 'when' ('Use for OGC services, server-side rendering, and georeferenced media content'), providing explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would use: WMS, WFS, WMTS, OGCFeatureLayer, KMLLayer, MapImageLayer, CatalogLayer, MediaLayer, OGC services, server-side rendering, georeferenced media. These are the exact terms a GIS developer would search for.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with very specific layer type names (WMS, WFS, WMTS, KMLLayer, etc.) that clearly carve out a niche. Unlikely to conflict with other skills unless there's another GIS/mapping skill, and even then the specific layer types differentiate it.

3 / 3

Total

11

/

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, highly actionable reference for ArcGIS advanced layer types with excellent executable code examples and a useful pitfalls section. Its main weakness is length — the document is a monolithic wall of code examples that could be better organized through progressive disclosure, and some examples follow repetitive patterns that could be condensed. The workflow clarity is adequate for a reference-style skill but lacks error handling guidance for multi-step operations.

Suggestions

Consider splitting detailed per-layer examples into separate referenced files (e.g., WMS.md, WFS.md, MediaLayer.md) and keeping only the comparison table and one basic example per layer type in the main SKILL.md.

Add error handling patterns for common failure modes (failed layer.load(), CORS errors, invalid sublayer IDs) since the pitfalls section identifies these issues but doesn't show how to handle them in code.

Reduce repetitive patterns — many examples follow the same create-configure-add structure and could be consolidated with a single annotated template plus a table of layer-specific properties.

DimensionReasoningScore

Conciseness

The skill is quite long (~500+ lines) and includes many code examples that are largely repetitive patterns (create layer, add to map). Some sections like the comparison table and import patterns are efficient, but the sheer volume of similar examples could be condensed. The common pitfalls section is valuable and concise, but the overall document could be tightened significantly.

2 / 3

Actionability

Every layer type has fully executable, copy-paste ready code examples with real URLs, proper imports, and complete configurations. The examples cover basic usage, advanced configurations (renderers, sublayers, joins), and even a full HTML page example. Code is concrete and specific throughout.

3 / 3

Workflow Clarity

The skill is primarily a reference catalog of layer types rather than a multi-step workflow, so explicit sequencing is less critical. However, some patterns like WFS capabilities discovery and CatalogLayer footprint querying involve multi-step processes that lack validation checkpoints (e.g., no error handling for failed loads, no guidance on what to do if capabilities discovery returns unexpected results).

2 / 3

Progressive Disclosure

The skill has good cross-references to related skills (arcgis-layers, arcgis-imagery, etc.) and a reference samples section pointing to external examples. However, the main document is monolithic with all layer types inline rather than splitting detailed examples into separate files. The comparison table at the top is a good overview, but the body could benefit from moving detailed examples to referenced files.

2 / 3

Total

9

/

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 (798 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.