arcgis-spatial-analysis
Perform spatial analysis using analysis objects, REST services for routing/geocoding/geoprocessing, and feature reduction with clustering/binning.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-spatial-analysis/SKILL.mdQuality
Discovery
67%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 is technically specific and lists concrete capabilities in the spatial analysis domain, making it distinctive. However, it lacks an explicit 'Use when...' clause and relies heavily on technical jargon that users may not naturally use, missing common trigger terms like 'maps', 'GIS', 'location', or 'directions'.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user needs spatial analysis, mapping, route planning, address geocoding, or geographic data processing.'
Include more natural user-facing trigger terms such as 'maps', 'GIS', 'location analysis', 'directions', 'address lookup', 'geographic data', or platform names like 'ArcGIS'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: spatial analysis using analysis objects, REST services for routing/geocoding/geoprocessing, and feature reduction with clustering/binning. These are concrete, identifiable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'spatial analysis', 'routing', 'geocoding', 'geoprocessing', 'clustering', 'binning', but these are somewhat technical. Missing more natural user terms like 'maps', 'GIS', 'location', 'directions', 'address lookup', or platform-specific terms like 'ArcGIS' or 'Esri'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of spatial analysis, routing/geocoding/geoprocessing REST services, and feature reduction with clustering/binning is a very specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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 spatial analysis with excellent executable code examples and useful anti-pattern documentation. Its main weakness is length—the inline coverage of 9+ analysis types makes it a large monolithic document that would benefit from progressive disclosure via separate reference files. Workflow clarity could be improved with explicit error handling and validation patterns.
Suggestions
Move detailed analysis type examples (SliceAnalysis, ShadowCastAnalysis, DimensionAnalysis, measurement analyses) into a separate ANALYSIS-TYPES.md reference file, keeping only ViewshedAnalysis and one measurement example in the main skill as representative patterns.
Add error handling patterns for common failure scenarios (e.g., adding analysis to MapView instead of SceneView, analysis computation failures) to improve workflow clarity.
Add a brief workflow summary at the top showing the general analysis lifecycle: create → add to view → set geometry → watch progress/result → handle errors.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient with code examples and avoids explaining basic concepts, but it's quite long (~400 lines) with many analysis types that could be split into separate reference files. Some brief descriptive comments (e.g., 'Analysis objects are added to a SceneView's analyses collection') are mildly redundant given the code examples demonstrate this. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready JavaScript code with correct import statements, constructor patterns, and result handling. The anti-pattern examples in Common Pitfalls are especially actionable, showing both wrong and correct approaches. | 3 / 3 |
Workflow Clarity | The ElevationProfileAnalysis example shows a clear workflow (create → add to view → set geometry → watch progress), and the interactive placement section shows abort handling. However, most analysis examples lack explicit validation/verification steps—there's no guidance on error handling for failed analyses or checking if SceneView is ready before adding analyses. | 2 / 3 |
Progressive Disclosure | The skill has good cross-references to related skills and reference samples at the bottom, but the main body is a monolithic document with 9+ analysis types fully inlined. The analysis types could be split into a separate reference file with only the most common patterns kept in the main skill, improving scannability. | 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (510 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.