Content
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable code examples covering all major Arcade use cases in ArcGIS, making it highly practical for implementation. However, it suffers from being overly long due to inline function reference tables that could be extracted to a separate file, and it lacks explicit workflow guidance for debugging or iterating on expressions. The content would benefit from trimming the reference sections and adding error handling patterns.
Suggestions
Extract the 'Common Arcade Functions' section (~60 lines of function reference) into a separate ARCADE_REFERENCE.md file and link to it from the main skill
Add a brief debugging workflow with explicit steps: write expression → test with Console() → check for null values → validate output format
Remove the introductory 'Arcade is an expression language for ArcGIS' section and bullet list of uses — Claude already knows this from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like listing basic Arcade concepts Claude would already know (e.g., explaining what Arcade is used for, basic variable syntax). The function reference tables are extensive and border on reference documentation that could be linked rather than inlined. However, the code examples themselves are reasonably tight. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples across all major use cases: popups, renderers, labels, programmatic execution, and TypeScript usage. Each example is concrete with realistic field names and complete configuration objects. | 3 / 3 |
Workflow Clarity | The skill is organized by use case (popups, renderers, labels, etc.) which provides implicit sequencing, but there are no explicit workflows for multi-step processes like debugging expressions or iterating on complex Arcade logic. The 'Execute Arcade Programmatically' section has a clear sequence but lacks validation/error handling steps. | 2 / 3 |
Progressive Disclosure | The skill is largely monolithic at ~250 lines with extensive inline function reference tables that would be better in a separate REFERENCE.md file. There is one cross-reference to the arcgis-core-maps skill and reference samples are mentioned, but the bulk of content (especially Common Arcade Functions) bloats the main file unnecessarily. | 2 / 3 |
Total | 9 / 12 Passed |