check-chokepoint-status
Retrieve live disruption status for the 13 monitored maritime chokepoints (Suez, Hormuz, Malacca, Bab el-Mandeb, Panama, and more). Use when the user asks whether a strait or canal is disrupted, congested, or safe for shipping right now.
68
83%
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.
W007: Insecure credential handling detected in skill instructions.
What this means
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.
Why it was flagged
The skill explicitly requires an API key in the X-WorldMonitor-Key header and embeds a literal-looking API key value in the doc (wm_012345...), which encourages or enables the LLM to include secret values verbatim in generated requests or code.
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
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.
Why it was flagged
The document contains a literal, high-entropy API key-like value on line 10: "wm_0123456789abcdef0123456789abcdef01234567". It is not a placeholder (e.g., YOUR_API_KEY, sk-xxxx) or an environment variable name; it is a concrete key-like string with random-looking hex characters and therefore meets the definition of a secret. I did not flag other lines because they are non-sensitive (endpoints, timestamps, example env var $WM_API_KEY, or example JSON) and do not contain high-entropy literal credentials.
- Repository
- koala73/worldmonitor
- Commit
23ab7d1
- Audited
- Security analysis
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.