arcgis-core-maps

Create 2D and 3D maps using ArcGIS Maps SDK for JavaScript. Use for initializing maps, scenes, views, and navigation. Supports both Map Components (web components) and Core API approaches.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./contexts/4.34/skills/arcgis-core-maps/SKILL.md

Quality

Content

57%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill excels at actionability with comprehensive, executable code examples covering both Map Components and Core API approaches. However, it suffers from being too monolithic—cramming reference material (esriRequest, promiseUtils, planetary visualization, TypeScript autocasting) into what should be a focused core maps skill. The content would benefit significantly from splitting advanced topics into separate files and adding a clearer getting-started workflow.

Suggestions

Split advanced/tangential topics (esriRequest, promiseUtils, reactiveUtils, planetary visualization, autocasting/TypeScript) into separate referenced files, keeping SKILL.md focused on core map/scene creation with brief links to these resources.

Add a clear 'Quick Start' workflow at the top with numbered steps and a validation checkpoint (e.g., 'Verify the map renders by checking the browser console for errors').

Trim the autocasting section significantly—the TypeScript best practices around discriminated unions are useful but overly detailed for a maps skill; move to a dedicated TypeScript patterns file.

Add a brief table of contents or navigation section at the top so Claude can quickly find the relevant section rather than scanning 400+ lines.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~400+ lines) and includes some sections that could be trimmed or split out (e.g., the autocasting/TypeScript section, planetary visualization, promiseUtils, esriRequest). The autocasting guidance is useful but verbose for a 'Core Maps' skill. However, most content is code examples rather than explanatory prose, which helps.	2 / 3
Actionability	Nearly every section provides fully executable, copy-paste ready code examples covering both Map Components and Core API approaches. HTML boilerplate, JavaScript imports, and CSS requirements are all explicitly shown with complete working examples.	3 / 3
Workflow Clarity	The skill covers many features but lacks explicit step-by-step workflows with validation checkpoints. The Common Pitfalls section helps with error prevention, but there's no clear sequenced workflow for setting up a map from scratch (e.g., 'Step 1: Add CSS, Step 2: Create container, Step 3: Initialize map, Step 4: Verify rendering'). The content reads more as a reference than a guided process.	2 / 3
Progressive Disclosure	This is a monolithic wall of content with no references to external files for advanced topics. Sections like planetary visualization, esriRequest, promiseUtils, reactiveUtils, and the autocasting/TypeScript guide should be split into separate reference files. The skill tries to be both a quick-start guide and a comprehensive reference, making it hard to navigate.	1 / 3
	Total	8 / 12 Passed

Description

100%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.

This is a strong skill description that clearly identifies the technology (ArcGIS Maps SDK for JavaScript), lists specific capabilities (2D/3D maps, scenes, views, navigation), provides explicit 'Use for' guidance, and distinguishes between two implementation approaches. It uses proper third-person voice and includes domain-specific trigger terms that developers would naturally use.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Create 2D and 3D maps', 'initializing maps, scenes, views, and navigation', and distinguishes two approaches ('Map Components (web components) and Core API approaches').	3 / 3
Completeness	Clearly answers both what ('Create 2D and 3D maps using ArcGIS Maps SDK for JavaScript') and when ('Use for initializing maps, scenes, views, and navigation') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'ArcGIS', 'Maps SDK', 'JavaScript', '2D', '3D', 'maps', 'scenes', 'views', 'navigation', 'web components', 'Core API'. These cover the terms a developer working with ArcGIS would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — the combination of 'ArcGIS Maps SDK for JavaScript' with specific concepts like scenes, views, Map Components, and Core API creates a clear niche that is unlikely to conflict with other mapping or JavaScript skills.	3 / 3
	Total	12 / 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 (810 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: SaschaBrunnerCH/arcgis-maps-sdk-js-ai-context
Path: contexts/4.34/skills/arcgis-core-maps/SKILL.md
Commit: d84407b

Reviewed: 5 days 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.