arcgis-coordinates-projection

Work with coordinate systems, projections, and coordinate conversion. Use for transforming coordinates and displaying position in multiple formats.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./contexts/4.34/skills/arcgis-coordinates-projection/SKILL.md

Quality

Content

64%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with excellent executable code examples covering coordinate conversion, projection, and formatting in ArcGIS. Its main weaknesses are length (the deprecated APIs section and full HTML example inflate the document) and lack of explicit workflow sequencing with validation checkpoints. The deprecation handling is well-structured with a clear migration table, though the legacy code examples could be moved to a separate file.

Suggestions

Move the deprecated APIs section (legacy code examples) to a separate DEPRECATED.md file, keeping only the migration table in SKILL.md

Add explicit validation/verification steps after projection operations (e.g., check that projected geometry has expected spatial reference, verify coordinate values are in expected range)

Consider moving the complete HTML example to a separate EXAMPLE.md file and linking to it, to reduce the main skill's token footprint

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some sections that could be tightened. The deprecated APIs section with legacy code examples adds bulk, and some sections like 'Common Spatial References' list things Claude likely knows. However, most content is code-focused without excessive prose.	2 / 3
Actionability	Excellent actionability with fully executable code examples throughout—HTML components, JavaScript imports, widget configuration, coordinate formatting, and a complete working HTML example. All code is copy-paste ready with real import paths and API calls.	3 / 3
Workflow Clarity	Individual operations are clear, but there's no explicit workflow sequencing for multi-step processes like 'load engine → project → verify result.' The async load requirement is mentioned in pitfalls but not enforced as a validation checkpoint in the workflow. The complete example demonstrates a workflow implicitly but lacks explicit validation steps.	2 / 3
Progressive Disclosure	The skill has good section organization and one cross-reference to arcgis-geometry-operations, plus reference samples at the bottom. However, the document is quite long (~200+ lines of content) with the deprecated APIs section and complete HTML example inline, which could be split into separate files. The migration table is well-structured but the legacy code examples could be in a separate reference.	2 / 3
	Total	9 / 12 Passed

Description

67%Scale 1-3

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 adequately covers both what the skill does and when to use it, earning good marks for completeness. However, it lacks specific concrete actions and misses many natural trigger terms users would employ (e.g., 'lat/long', 'UTM', 'EPSG', 'GPS'). Adding more specific capabilities and common user vocabulary would significantly improve skill selection accuracy.

Suggestions

Add specific concrete actions such as 'convert between lat/long and UTM', 'reproject between EPSG codes', 'parse DMS/decimal degree notation' to improve specificity.

Include natural trigger terms users would say: 'latitude', 'longitude', 'lat/long', 'UTM', 'EPSG', 'GPS coordinates', 'WGS84', 'map projection', 'CRS' to improve discoverability.

Dimension	Reasoning	Score
Specificity	Names the domain (coordinate systems, projections) and some actions (transforming coordinates, displaying position in multiple formats), but lacks specific concrete actions like 'convert between UTM and lat/long', 'reproject shapefiles', or 'parse DMS notation'.	2 / 3
Completeness	Clearly 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 terms like 'coordinate systems', 'projections', 'coordinate conversion', and 'position', but misses many natural user terms such as 'lat/long', 'latitude', 'longitude', 'UTM', 'EPSG', 'GPS coordinates', 'WGS84', 'map projection', or 'CRS'.	2 / 3
Distinctiveness Conflict Risk	The domain of coordinate systems and projections is fairly specific, but 'coordinate systems' could overlap with skills related to GIS, mapping, or spatial data processing. More specific trigger terms (e.g., specific projection names or file formats) would reduce conflict risk.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: SaschaBrunnerCH/arcgis-maps-sdk-js-ai-context
Path: contexts/4.34/skills/arcgis-coordinates-projection/SKILL.md
Commit: d84407b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.