arcgis-geometry-operations
Create, manipulate, and analyze geometries using geometry classes and geometry operators. Use for spatial calculations, geometry creation, buffering, intersections, unions, and mesh operations.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly communicates both what the skill does and when to use it. It lists specific concrete operations (buffering, intersections, unions, mesh operations) that serve as effective trigger terms, and the 'Use for...' clause provides explicit guidance on when to select this skill. The description is concise, uses third person voice, and occupies a distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create, manipulate, and analyze geometries', 'spatial calculations', 'geometry creation', 'buffering', 'intersections', 'unions', and 'mesh operations'. These are concrete, identifiable operations. | 3 / 3 |
Completeness | Clearly answers both 'what' (create, manipulate, and analyze geometries using geometry classes and operators) and 'when' ('Use for spatial calculations, geometry creation, buffering, intersections, unions, and mesh operations'). The 'Use for...' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'geometries', 'spatial calculations', 'buffering', 'intersections', 'unions', 'mesh operations', 'geometry classes', 'geometry operators'. These cover the domain well and match how users would describe spatial/geometry tasks. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on geometry operations, spatial calculations, buffering, intersections, unions, and mesh operations creates a clear niche that is unlikely to conflict with other skills. The domain-specific terminology (geometry classes, geometry operators, mesh operations) makes it highly distinctive. | 3 / 3 |
Total | 12 / 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 geometry operations with excellent executable code examples covering the full API surface. Its main weaknesses are verbosity—the repetitive import/execute patterns across many operators could be condensed significantly—and the lack of explicit validation/error-handling workflows. The deprecated section is well-handled with a clear migration table.
Suggestions
Condense the spatial relationships section into a single example with a table listing all operators, rather than repeating the import/execute pattern 8 times with near-identical code.
Add error handling guidance—what to do when operator.load() fails, or when operations return null/unexpected results.
Consider splitting the detailed operator examples (measurements, manipulation, set operations) into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the most common patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400 lines) with some redundancy—e.g., the 'Importing Operators' section shows duplicate import patterns, and the spatial relationships section repeats the same import/execute pattern 8 times when a table + one example would suffice. The sentence 'The geometry operators module is the modern, recommended approach for geometry operations' is unnecessary filler. However, most content is code-focused and avoids explaining basic concepts. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready JavaScript code for every operation—geometry creation, buffer operations, spatial relationships, set operations, measurements, projections, and common patterns. Import paths are specific, parameters are shown with real values, and return types are noted. | 3 / 3 |
Workflow Clarity | The common patterns section shows multi-step workflows (buffer and query, calculate total area), and the pitfalls section addresses validation concerns like spatial reference mismatches and loading operators. However, there are no explicit validation checkpoints or error recovery steps—e.g., no guidance on what happens if operator.load() fails, or how to verify geometry validity after operations. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a summary table of available operators, plus reference samples at the end. However, this is a very long monolithic file that could benefit from splitting detailed operator references into separate files. The deprecated section is appropriately separated but adds significant length to the main file. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.