arcgis-map-tools
Interactive map tools including swipe comparison, measurement, identify, and routing. Use for layer comparison, distance/area measurement, and navigation services.
70
63%
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/4.34/skills/arcgis-map-tools/SKILL.mdQuality
Discovery
85%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 solid description that clearly identifies the skill's domain (interactive map tools) and lists specific capabilities. The 'Use for' clause provides explicit trigger guidance. The main weakness is that some trigger terms are somewhat technical ('swipe comparison', 'identify') and could benefit from more natural user-facing language variations.
Suggestions
Add more natural user-facing trigger terms such as 'directions', 'route planning', 'compare maps side by side', or 'GIS tools' to improve discoverability.
Clarify what 'identify' means in context (e.g., 'identify features on map' or 'click-to-identify map elements') since it's vague as a standalone term.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: swipe comparison, measurement, identify, and routing. Also specifies layer comparison, distance/area measurement, and navigation services. | 3 / 3 |
Completeness | Clearly answers both what (interactive map tools including swipe comparison, measurement, identify, routing) and when ('Use for layer comparison, distance/area measurement, and navigation services'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'map', 'measurement', 'routing', 'layer comparison', 'distance', 'area', and 'navigation', but misses common user terms like 'directions', 'route planning', 'compare maps', 'measure distance on map', or 'GIS'. Users might not naturally say 'swipe comparison' or 'identify'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of interactive map tools with specific capabilities like swipe comparison, measurement, identify, and routing creates a clear niche that is unlikely to conflict with other skills. The domain is well-defined and distinct. | 3 / 3 |
Total | 11 / 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.
The skill provides highly actionable, executable code examples across multiple ArcGIS map tools, which is its primary strength. However, it is severely bloated—particularly the print section which accounts for nearly half the content and should be extracted to a separate reference file. The lack of progressive disclosure and workflow validation steps significantly reduce its effectiveness as a skill document.
Suggestions
Extract the extensive Print section (templates, formats, configurations, custom workflows, legend, screenshots) into a separate PRINT.md file and reference it with a one-line link from the main skill.
Remove the print formats table and explanatory content that Claude already knows (e.g., what PDF, PNG, JPG are).
Add explicit validation/error handling steps to workflows—especially for routing (check API key validity, handle solve failures) and identify (handle empty results gracefully).
Consolidate redundant patterns: for each tool, show only the recommended approach (web component) with a brief note about the deprecated Core API alternative, rather than full code for both.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, with extensive print-related content that dominates the file (print templates, formats table, multiple print variations, screenshot alternatives). Many sections show redundant patterns (component + Core API + widget for the same feature). The print section alone could be its own referenced file. Claude doesn't need a table explaining what PDF, PNG, and JPG stand for. | 1 / 3 |
Actionability | All code examples are concrete, executable, and copy-paste ready with proper imports, complete configurations, and realistic usage patterns. The routing example shows a full click-to-route workflow, identify shows complete popup integration, and the complete example at the end is a fully functional HTML page. | 3 / 3 |
Workflow Clarity | Individual code blocks are clear but there's no explicit workflow sequencing or validation checkpoints. The routing section implicitly sequences (add stops → solve when 2+) but lacks error handling guidance. The 'Common Pitfalls' section hints at validation concerns (API keys, tolerance) but doesn't integrate them into workflows with explicit verification steps. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. The print section alone contains ~200 lines covering templates, formats, configurations, custom workflows, legend customization, and screenshots—all inline. The 'Reference Samples' section at the end lists sample names but doesn't link to actual files. Content should be split into separate files for print, routing, measurement, etc. | 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 (654 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.