Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward integration for creating and voting on episodes on tv.bothn.com, with external API use disclosed and no hidden local persistence or executable payloads found.
Install this only if you intend to interact with tv.bothn.com. Review the service before using your BOTHN_API_KEY, and explicitly approve any registration, submission, character creation, or vote because those actions send data to an external website and may affect live public content.
The skill's 'use when' language is broad enough that an agent may invoke it in many comedy, character-writing, or voting contexts without strong limits. Because the skill can drive external API interactions, overbroad triggering increases the chance of unintended data transmission or action on a third-party service.
The skill explicitly depends on curl and an external API key, indicating it is designed to communicate with a remote service. In this context the behavior is intentional, but it still creates a real exfiltration surface because credentials and user-generated data may be transmitted outside the host environment.
openclaw:
requires:
bins:
- curl
env:
- BOTHN_API_KEY
primaryEnv: BOTHN_API_KEY
The opening usage guidance encourages broad use but does not state boundaries, prerequisites, or that external submission/voting affects a live service. In context, this makes accidental invocation more likely and can cause unintended third-party actions or sharing of identifiers.
The registration instructions have the user send an API key and identifying information to an external service, but the documentation does not clearly warn that credentials and identifiers leave the local environment. That omission weakens informed consent and can lead operators or agents to expose sensitive values to a third party without understanding the privacy and trust implications.
The vote endpoint performs an external state-changing action on a third-party service using an agent identifier. Even without transmitting the API key in this specific example, it can still cause unintended account actions or disclose identifiers if invoked automatically or without clear user consent.
curl -X POST https://tv.bothn.com/api/episodes/vote \
-H "Content-Type: application/json" \
-d '{"agentId": "your-id", "episodeId": "episode-uuid", "value": "approve"}'