arcgis-interaction
Handle user interaction with map views including hit testing, feature highlighting, sketching, and event handling.
65
57%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-interaction/SKILL.mdQuality
Discovery
42%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 does a reasonable job listing specific map interaction capabilities (hit testing, feature highlighting, sketching, event handling), giving it good specificity. However, it critically lacks a 'Use when...' clause, which hurts completeness significantly. The trigger terms are somewhat technical and could benefit from more natural language variations and framework-specific references.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs to handle clicks on a map, select or highlight map features, draw shapes on a map, or respond to map interaction events.'
Include natural language variations and common user phrases like 'click on map', 'draw on map', 'select map feature', 'map tap', along with any specific framework names (e.g., MapKit, Leaflet, Mapbox) if applicable.
Specify the technology or platform context (e.g., web maps, iOS MapKit, ArcGIS) to reduce conflict risk with other UI interaction skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: hit testing, feature highlighting, sketching, and event handling. These are distinct, identifiable capabilities within the map interaction domain. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores at the lower end. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'map views', 'hit testing', 'sketching', and 'feature highlighting', but these are somewhat technical. Missing common user-facing terms like 'click on map', 'draw on map', 'select features', 'map click events', or specific framework references (e.g., MapKit, Leaflet, Mapbox). | 2 / 3 |
Distinctiveness Conflict Risk | The 'map views' domain is fairly specific, but 'event handling' is very broad and could overlap with general UI/interaction skills. Without specifying a particular mapping framework or technology, there's moderate overlap risk with other UI interaction skills. | 2 / 3 |
Total | 8 / 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 skill covering ArcGIS map interaction patterns with excellent actionability through executable code examples and good progressive disclosure. Its main weaknesses are moderate verbosity (could trim some table documentation and consolidate similar examples) and lack of explicit multi-step workflows with validation checkpoints. The Common Pitfalls section with anti-pattern/correct-pattern pairs is a notable strength.
Suggestions
Consider trimming the Sketch Component tables (attributes, events, methods) into a separate reference file to reduce the main skill's length while maintaining the quick-start examples inline.
Add a brief workflow sequence for common multi-step interaction patterns (e.g., 1. Wait for view ready → 2. Set up layer view → 3. Attach event handlers → 4. Implement cleanup), especially around resource lifecycle management.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but is quite long (~400 lines). Some sections like the Sketch Component tables and the hit test result types table add bulk. The note about CDN vs ESM imports is repeated context. However, it generally avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Excellent actionability throughout. Every section provides fully executable, copy-paste ready code examples covering hit testing, highlighting, sketching, event handling, and coordinate conversion. The complete HTML example at the end is particularly strong. | 3 / 3 |
Workflow Clarity | Individual code snippets are clear, but there's no explicit multi-step workflow with validation checkpoints. The Common Pitfalls section provides good anti-pattern/correct-pattern pairs which serve as implicit guidance, but the skill lacks sequenced workflows for combining these interactions (e.g., setup → interact → cleanup lifecycle). | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from simple (hit testing) to complex (complete examples). References to related skills (arcgis-popup-templates, arcgis-editing, arcgis-core-maps) are one level deep and clearly signaled. Reference samples section provides good pointers for further exploration. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%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 (529 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.