arcgis-rest-services

REST service wrappers for routing, geocoding, printing, places, geoprocessing, and other server-side operations in ArcGIS Maps SDK for JavaScript

Quality

48%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./contexts/4.34/skills/arcgis-rest-services/SKILL.md

Quality

Discovery

32%

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 identifies the domain and lists several capability areas but reads more like a category label than an actionable skill description. It lacks concrete actions (verbs describing what the skill does), natural user-facing trigger terms, and any explicit 'Use when...' guidance, making it difficult for Claude to reliably select this skill at the right time.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to call ArcGIS REST services for directions, address geocoding, map printing, place search, or server-side geoprocessing tasks.'

Replace category nouns with concrete action phrases, e.g., 'Calculate driving/walking routes, convert addresses to coordinates, generate printable maps, search for nearby places, and run server-side geoprocessing jobs.'

Include natural user trigger terms and file/format references such as 'directions', 'address lookup', 'find nearest', 'map export', 'spatial analysis', and 'ArcGIS REST API'.

Dimension	Reasoning	Score
Specificity	Names the domain (ArcGIS Maps SDK for JavaScript) and lists several action areas (routing, geocoding, printing, places, geoprocessing), but these are category names rather than concrete actions like 'calculate driving routes' or 'convert addresses to coordinates'.	2 / 3
Completeness	Describes what the skill covers (REST service wrappers for various operations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately clear, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant technical keywords like 'routing', 'geocoding', 'printing', 'places', 'geoprocessing', and 'ArcGIS Maps SDK for JavaScript', but misses natural user phrasings like 'find directions', 'address lookup', 'map services', 'spatial analysis', or 'REST API'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'ArcGIS Maps SDK for JavaScript' and 'REST service wrappers' provides some distinctiveness, but terms like 'routing', 'geocoding', and 'geoprocessing' could overlap with other GIS or mapping skills if multiple exist in the skill set.	2 / 3
	Total	7 / 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 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

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (685 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: SaschaBrunnerCH/arcgis-maps-sdk-js-ai-context
Commit: d84407b

Reviewed: 1 day 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.