arcgis-coordinates-projection
Work with coordinate systems, projections, and coordinate conversion. Use for transforming coordinates and displaying position in multiple formats.
76
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-coordinates-projection/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description covers the basics with a clear domain focus on coordinate systems and conversions, and includes an explicit 'Use for' clause. However, it lacks specific concrete actions and misses many natural trigger terms users would employ (e.g., 'lat/long', 'UTM', 'GPS', 'EPSG'). Adding more specific capabilities and common user vocabulary would significantly improve skill selection accuracy.
Suggestions
Add specific concrete actions like 'convert between lat/long and UTM', 'reproject between coordinate reference systems', 'parse DMS/decimal degree formats'.
Include natural trigger terms users would say: 'latitude', 'longitude', 'GPS coordinates', 'UTM', 'EPSG', 'WGS84', 'map projection', 'geospatial'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (coordinate systems, projections) and some actions (transforming coordinates, displaying position in multiple formats), but doesn't list specific concrete actions like 'convert between UTM and lat/long', 'reproject shapefiles', or 'parse DMS notation'. | 2 / 3 |
Completeness | Answers both 'what' (work with coordinate systems, projections, coordinate conversion) and 'when' ('Use for transforming coordinates and displaying position in multiple formats'), with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'coordinate systems', 'projections', 'coordinate conversion', and 'position', but misses common user terms like 'lat/long', 'latitude', 'longitude', 'UTM', 'EPSG', 'GPS coordinates', 'WGS84', 'CRS', or 'geospatial'. | 2 / 3 |
Distinctiveness Conflict Risk | The coordinate/projection domain is fairly specific, but 'coordinate systems' and 'projections' could overlap with skills related to general GIS, mapping, or even mathematical coordinate geometry. More specific trigger terms would reduce conflict risk. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, comprehensive reference skill for ArcGIS coordinate systems and projections. Its greatest strength is actionability — nearly every concept is backed by executable code with proper imports and expected outputs. The migration table and common pitfalls add significant practical value. Minor weaknesses include some verbosity that could be trimmed and the lack of explicit multi-step workflows with validation checkpoints for common coordinate conversion tasks.
Suggestions
Consider adding a brief end-to-end workflow example (e.g., 'Convert NAD83 coordinates to WGS84 with validation') that shows the complete sequence with explicit validation/error-checking steps.
Trim minor explanatory phrases like 'The recommended way to project geometries client-side' and 'For complex projections or when the client-side engine is insufficient' — the section headers and code make these self-evident.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples and tables, but some sections could be tightened. The import patterns section showing both ESM and CDN is useful but the skill is quite long. Some explanatory text like 'The recommended way to project geometries client-side' and 'For complex projections or when the client-side engine is insufficient' add minor verbosity. The common pitfalls section, while useful, explains some things Claude would know (like async loading patterns). | 2 / 3 |
Actionability | Excellent actionability throughout — nearly every section includes fully executable, copy-paste ready code examples with correct import paths, method signatures, and expected outputs. The coordinate formatter section even shows example output strings. The migration table provides direct before/after replacements. | 3 / 3 |
Workflow Clarity | Individual operations are clearly documented, but there's no explicit multi-step workflow with validation checkpoints. The common pitfalls section addresses the critical 'load before use' pattern, but the skill doesn't present a sequenced workflow for common tasks like 'convert coordinates from one system to another' with validation steps. For a reference-style skill this is acceptable but not exemplary. | 2 / 3 |
Progressive Disclosure | Well-structured with clear section headers, a logical progression from simple (components) to complex (geodetic operations), and appropriate cross-references to related skills at the end. Reference samples are listed for deeper exploration. Content is appropriately contained in one file given its scope, with clear pointers to related skills for adjacent topics. | 3 / 3 |
Total | 10 / 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.