Implement authentication with ArcGIS using OAuth 2.0, API keys, and identity management. Use for accessing secured services, portal items, and user-specific content.
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Security
2 findings — 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Insecure credential handling detected (high risk: 1.00). The skill's examples instruct embedding API keys, app IDs, and tokens directly as string literals (e.g., esriConfig.apiKey = "YOUR_API_KEY", registerToken({ token: "YOUR_TOKEN" })) and even logging tokens, which encourages the LLM to place secret values verbatim into generated code/output.
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.
Potentially malicious external URL detected (high risk: 0.80). The skill includes a runtime CDN script tag that loads and executes remote JavaScript from https://js.arcgis.com/5.0/, which is a required dependency for the CDN usage and therefore fetches and runs remote code at runtime.
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.