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.
76
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-core-maps/SKILL.mdQuality
Discovery
100%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 usage triggers, and distinguishes between two supported approaches. It uses proper third-person voice and contains natural keywords that developers would use when seeking this skill.
| 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 capabilities like scenes, views, and the two API approaches creates a clear niche that is unlikely to conflict with other mapping or JavaScript skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent, executable code examples and a valuable Common Pitfalls section with anti-patterns. However, it severely suffers from scope creep and verbosity—it tries to be a comprehensive API reference rather than a focused skill for creating maps. Content like HTTP requests, Mars visualization, reactive utilities, and synchronized views should be extracted into separate files and referenced from a much leaner overview.
Suggestions
Extract esriRequest, promiseUtils, reactiveUtils, planetary visualization, and overview map sections into separate referenced skill files to reduce this skill to its core scope of map/scene creation.
Remove the reference tables for view events, view state properties, and map properties—these are API documentation that Claude can look up, not actionable skill content.
Consolidate the autocasting section into a brief recommendation with a link to a separate TypeScript patterns reference file.
Add a brief decision workflow at the top: 'Use Map Components for new projects, Core API when you need programmatic control' to help Claude choose the right approach quickly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~500+ lines. It includes extensive reference tables (basemaps, view events, map properties, view state properties), multiple redundant examples showing both Map Components and Core API for every concept, and sections like esriRequest, planetary visualization (Mars), and overview maps that go well beyond the stated scope of 'creating 2D and 3D maps.' Much of this content (event handling patterns, HTTP requests, reactive utilities) belongs in separate referenced files. | 1 / 3 |
Actionability | The code examples are fully executable and copy-paste ready, including complete HTML boilerplates with proper CDN links, CSS, and script tags. The Common Pitfalls section provides excellent anti-pattern/correct-pattern pairs with clear impact descriptions. | 3 / 3 |
Workflow Clarity | For a simple skill (creating maps), the individual steps are clear, but there's no clear sequencing guidance for when to use which approach (Map Components vs Core API) beyond 'Modern - Recommended.' The CDN setup sections provide good step-by-step HTML templates, but the overall document lacks a clear workflow progression from setup to working map. | 2 / 3 |
Progressive Disclosure | Despite having a 'Related Skills' section at the bottom referencing arcgis-layers, arcgis-starter-app, etc., the skill itself is a monolithic wall of content. Sections like esriRequest, promiseUtils, reactiveUtils, planetary visualization, and overview maps should be in separate referenced files. The autocasting section alone is substantial enough to warrant its own reference document. | 1 / 3 |
Total | 7 / 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 (854 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.