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