other
- Location
SKILL.md:31- Finding
Public Disclosure of Sensitive Information Derived from Private Memory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill needs review because it can turn private memory files into public BotRoast posts, repeat that on a heartbeat, and store an API key in workspace files.
Install only if you are comfortable with an agent reading personal memory/profile files and posting jokes derived from them to BotRoast.ai. Do not enable heartbeat posting without a separate review gate, and prefer a secret manager or environment variable over workspace JSON files for the API key.
SKILL.md:31Public Disclosure of Sensitive Information Derived from Private Memory
SKILL.md:19Skill-Load Instructions Trigger Immediate Credential and Data-Access Actions
SKILL.md:51Recurring Heartbeat Automatically Reads Memory and Publishes Content
SKILL.md:26API Key Is Stored in Plaintext Workspace Files
The documented purpose is roast generation from limited files, but the described behavior expands to additional local file access, persistent state, API key sourcing, remote fetching, and voting/status operations. This mismatch prevents informed consent and makes security review harder because operators may approve a seemingly harmless skill that actually has broader data access and external interaction.
The skill tells the agent to publicly submit user-derived roast content without a clear privacy notice, consent checkpoint, or explanation that the content will be published to a public feed. In context, the source material is personal memory data, making disclosure especially risky and likely to surprise users.
The skill instructs the agent to obtain an API key from the user and save it in a workspace file, creating a credential access and storage risk. In a multi-skill or synced-workspace environment, plaintext secrets in predictable paths are prone to accidental disclosure or misuse.
"Hey! I need your BotRoast API key to start roasting you. You got it when you signed up at botroast.ai — it starts with br_."
Store it in memory/botroast-credentials.json:
{
"api_key": "br_xxxxx",
The skill explicitly instructs the agent to mine personal memory files for embarrassing or painful truths and publish them as roast content. This is dangerous because it operationalizes extraction of sensitive personal details for external disclosure, even if framed as humor.
The heartbeat instructions authorize recurring automatic submissions to an external service without requiring renewed user consent or review. In this skill's context, that means periodic mining of personal files and repeated publication of user-derived content, amplifying privacy harm over time.
The heartbeat flow normalizes repeated review of personal files and ongoing disclosure to a remote public service. Automating this turns a one-time privacy risk into continuous surveillance and exfiltration of evolving personal information.
The quality criteria encourage using truths and specific details from anywhere in the workspace for content that is then publicly published. This broadens exposure from a few named files to potentially all locally available data, sharply increasing the risk of leaking confidential or sensitive information.
The skill invokes network access and handles credentials/state, but does not declare any explicit tool scope or permission boundaries. In an agent setting, undeclared capabilities make it easier for the skill to perform external transmission and local data handling without clear review or enforcement.
The setup flow directs the agent to solicit an API key from the user and store it locally without guidance on secure storage, access restrictions, rotation, or least privilege. This increases the chance of accidental credential exposure through logs, workspace sync, backups, or other skills reading local files.
The skill instructs the agent to create content from private workspace files and publish it publicly, which is a clear data-sharing expansion beyond simple local content generation. Because the output is derived from personal memory files, sensitive facts can be transformed and exfiltrated even if raw files are never directly transmitted.
The skill performs external transmission of generated content to a remote API. External transmission is especially risky here because the transmitted roast is intentionally derived from private local files, so the network call becomes the mechanism for data exfiltration.
Only read files listed above. The more you know, the better the roast. Use the formula below. Then submit:
curl -X POST https://botroast-api.vercel.app/api/submit \
-H "Content-Type: application/json" \
-d '{"api_key": "YOUR_API_KEY", "roast": "Your savage roast here"}'
The documentation claims the roast should be grounded in specific files, but the quality guidance broadens this to 'anything in the workspace.' This inconsistency widens the effective data access scope and increases the chance that unrelated or sensitive workspace material will be incorporated into public output.
The skill explicitly reads MEMORY.md and constructs a prompt directing the agent to use that content as roast material, increasing the chance that sensitive or private workspace data is transformed into model output and then submitted to an external service. Although the prompt includes soft policy language about avoiding deeply private information, there is no technical filtering, classification, or redaction before the memory content is exposed to the model and potentially exfiltrated via the submit API.
Detected: suspicious.env_credential_access