Content
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 |