Retrieve the curated energy disruption event log for pipelines and storage facilities. Use when the user asks what energy assets are disrupted, sanctioned, offline, or under watch.
68
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
2 findings: 2 high 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.
The prompt includes a concrete API key-like string (wm_012345...) and mandates supplying an API key in the X-WorldMonitor-Key header, which could encourage embedding secrets verbatim in outputs even though a secure env-var curl example is also provided.
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
The snippet on SKILL.md line 10 contains a concrete, high-entropy API key-like value: "wm_0123456789abcdef0123456789abcdef01234567". It is not a generic placeholder (e.g., YOUR_API_KEY or sk-xxxx) nor a simple/setup password. The string has long, random-looking hex content and a service prefix, so it meets the definition of a literal credential that could be usable. Although presented in documentation, it is a real-looking hardcoded key and should be treated as a secret.
Low
Low-risk findings.
1 low severity finding. 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 required workflow calls a WorldMonitor API endpoint and ingests the returned JSON fields like `shortDescription` and `sources.title/url` into the agent context at runtime, where those description/source strings are populated from external evidence bundles (outsider-authored content).
23ab7d1
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.