Content
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 REST services with excellent executable code examples covering routing, geocoding, places, geoprocessing, and more. Its main weaknesses are its length (could benefit from splitting into sub-files with a concise overview), lack of validation steps in destructive operations like feature edits, and some redundancy in repeated import patterns across examples.
Suggestions
Split the monolithic content into separate reference files (e.g., ROUTING.md, GEOCODING.md, PLACES.md, GEOPROCESSING.md) and make SKILL.md a concise overview with the import pattern, authentication setup, and links to each service's detailed guide.
Add validation/verification steps to the Apply Edits section — check addResult/updateResult/deleteResult for errors before proceeding, and show a pattern for rolling back or handling partial failures.
Remove redundant import statements from each section after the first example, and instead reference the import pattern section (e.g., 'Import pattern: see above') to reduce token usage.
Convert the 'Reference Samples' section into actual hyperlinks to documentation or sample code repositories rather than bare text labels.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400+ lines) and covers many services exhaustively with full code examples. While each example is useful, the sheer volume makes it a reference document rather than a lean skill. Some sections (like the migration table with 9 entries) could be trimmed, and the consistent import pattern is repeated in every example rather than stated once. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready code examples with real service URLs, proper imports, parameter configuration, and result handling. The code is concrete and specific, not pseudocode, covering the full lifecycle from setup to consuming results. | 3 / 3 |
Workflow Clarity | The geoprocessor async section shows a clear multi-step workflow (submit → wait → fetch results) with status monitoring. However, the Apply Edits section involves destructive operations (add/update/delete) without validation checkpoints or confirmation steps. Error handling is mentioned in Common Pitfalls but not integrated into the workflow examples themselves. | 2 / 3 |
Progressive Disclosure | The content is a monolithic document with all service examples inline. While it has clear section headers, the 400+ lines of code examples would benefit from being split into separate reference files (e.g., ROUTING.md, GEOCODING.md, PLACES.md) with the main SKILL.md serving as a concise overview with links. The 'Reference Samples' section hints at external resources but provides no actual links. | 2 / 3 |
Total | 9 / 12 Passed |