Handle user interaction with map views including hit testing, feature highlighting, sketching, and event handling. Use for interactive map applications with feature selection and custom interactions.
52
57%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./contexts/4.34/skills/arcgis-interaction/SKILL.mdLow
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The skill's examples and workflow (see "Complete Example: Hit Test with Highlight" and other SKILL.md snippets) create FeatureLayer instances from public URLs (e.g., https://services3.arcgis.com/.../FeatureServer/0) and use hitTest/popup/graphic.attributes to read and act on those remote, user-provided feature contents, which could contain untrusted instructions that influence subsequent actions.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Yes — the HTML example loads remote ArcGIS scripts (https://js.arcgis.com/5.0/ and https://js.arcgis.com/5.0/map-components/) at runtime which fetch and execute JavaScript required for the skill, so these external URLs execute remote code used by the agent.
d84407b
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.