Security audit
Security checks for vulnerabilities and agentic risk
This note-taking skill is coherent, but it would automatically save exact wording from most user messages into persistent notes, so it needs review before installation.
Install only if you intentionally want ambient knowledge capture across conversations. Before using it with sensitive work, confirm where notes are stored, who can access them, how to disable capture, how to delete captured entries, and whether exact quotes can be replaced with summaries or redacted by default.
The skill is explicitly designed for always-on capture of inbound user messages and describes logging/capture behavior without any user-facing notice, consent, or privacy boundary. Because it operates ambiently and persistently, users may disclose sensitive personal, business, or credential-adjacent information that is then retained unexpectedly.
The skill mandates collection from every substantive user message, in parallel, with exact phrasing and provenance, which amounts to broad surveillance-style harvesting of natural-language content. In context, this is more dangerous because it is silent, continuous, and framed as non-blocking background behavior, making overcollection and unnoticed retention very likely.
These instructions direct the agent to write user-derived content into notes, project indexes, dashboards, or the knowledge base, creating persistent storage of user messages and inferred ideas. Persisting exact user phrasing and cross-linked facts without warning or consent materially increases privacy, confidentiality, and downstream disclosure risk.
The required output format logs exact quoted user phrasing, encouraging verbatim retention of potentially sensitive statements, secrets, regulated data, or proprietary ideas. Quoted logging also increases the chance that confidential content is later surfaced through search, sharing, sync, backups, or other downstream knowledge-base operations.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Paraphrasing or smoothing the user's language — keep the original voice
- Blocking the main conversation to finish capture — spawn or defer
- Creating knowledge pages for every passing mention — apply the notability gate
- Over-writing existing knowledge base material without checking what's there first
- Capturing purely operational exchanges as signal
No suspicious patterns detected.