CtrlK
BlogDocsLog inGet started
Tessl Logo

arcgis-advanced-layers

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

59

Quality

68%

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-advanced-layers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%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 comprehensive reference for ArcGIS advanced layer types with strong actionability through executable code examples. Its main weaknesses are its length (could benefit from splitting detailed sections like MediaLayer into separate files) and the lack of error handling/validation guidance for operations involving remote OGC services that can fail. The Common Pitfalls section is a nice addition but could be integrated into workflows with explicit recovery steps.

Suggestions

Split the MediaLayer section (and potentially other large sections) into separate reference files, keeping only a brief overview and link in the main SKILL.md to improve progressive disclosure.

Add error handling patterns for loading remote OGC services (e.g., try/catch around layer.load(), checking for CORS errors, validating service capabilities before use).

Trim redundant examples - the MediaLayer 'Complete Example' largely repeats the 'Multiple Images' pattern; consolidate or remove duplicative code blocks.

DimensionReasoningScore

Conciseness

The skill is quite long (~500+ lines) with many code examples that are largely variations of similar patterns. Some sections like the MediaLayer complete example repeat patterns already shown. However, it avoids explaining basic concepts Claude would know and stays focused on code.

2 / 3

Actionability

Nearly every section provides fully executable, copy-paste ready code examples with real URLs, complete import statements, and specific property configurations. The examples cover basic through advanced usage patterns for each layer type.

3 / 3

Workflow Clarity

The skill is primarily a reference catalog of layer types rather than a multi-step workflow. While individual examples show sequences (e.g., load layer → find sublayer → configure), there are no explicit validation checkpoints or error handling patterns for operations that could fail (like loading remote OGC services).

2 / 3

Progressive Disclosure

The content is a monolithic file with all layer types inline. The reference samples section at the end points to external examples, but the bulk of the content (especially MediaLayer which takes up nearly half the file) could be split into separate reference files with the SKILL.md serving as an overview with links.

2 / 3

Total

9

/

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 effectively identifies a clear niche in GIS/mapping layer management with strong, domain-specific trigger terms that would help Claude distinguish this skill from others. However, it lacks concrete action verbs (relying on the vague 'Work with') and the 'Use for' clause could be strengthened into a more explicit 'Use when...' trigger guidance with user-facing scenarios.

Suggestions

Replace 'Work with' with specific concrete actions like 'Configure, query, and display advanced layer types including...'

Rewrite the trigger clause as 'Use when the user needs to add or configure OGC service layers (WMS, WFS, WMTS), set up server-side rendered MapImageLayers, overlay georeferenced media, or work with CatalogLayers and dynamic data sources.'

DimensionReasoningScore

Specificity

The description names specific layer types (WMS, WFS, WMTS, etc.) and mentions some actions like 'server-side rendering' and 'georeferenced media content,' but it doesn't list concrete actions the skill performs (e.g., 'add layers,' 'configure services,' 'query features'). 'Work with' is vague.

2 / 3

Completeness

The 'what' is partially addressed (work with advanced layer types) and there is a 'Use for' clause, but it reads more like a category description than explicit trigger guidance. The 'when' is implied through 'Use for OGC services, server-side rendering, and georeferenced media content' but lacks a proper 'Use when...' clause with user-facing trigger scenarios.

2 / 3

Trigger Term Quality

Includes many natural keywords a GIS developer would use: WMS, WFS, WMTS, OGCFeatureLayer, MapImageLayer, CatalogLayer, MediaLayer, OGC services, server-side rendering, georeferenced media. These are specific technical terms users in this domain would naturally mention.

3 / 3

Distinctiveness Conflict Risk

The description targets a very specific niche—advanced GIS layer types and OGC services—with highly distinctive trigger terms like WMS, WFS, WMTS, CatalogLayer, and MediaLayer. This is 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 (715 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.