>- people's private information, confidential work, and anything the user would not want synced or backed up. Use this skill when the user asks about privacy, is about to share or sync the vault, has just imported chat history or meeting notes, or asks what is sensitive in their notes. Do NOT use to delete anything on your own, or as a substitute for the publishing check.
npx skills add https://github.com/undefined-ui/second-brain-os --skill second-brain-privacy
A mature vault is one of the highest-signal documents about a person that
exists, and it lives in a folder that gets synced, committed, backed up and
occasionally shared. Every copy is another place the content exists.
Find and report. Delete nothing without an explicit instruction naming what to
remove.
Check .obsidian/plugins/ too, where plugin data lives.
anything told in confidence, health or financial detail about someone else.
expensive version of this problem.
Critical: <credentials, must be removed and rotated>
High: <other people's private information>
Review: <material the user should decide about>
Repo visibility: <public | private> - <verdict>
Never quote the credential itself in the report. Name the file and the type.
Redaction after ingest is unreliable, because material has already propagated
into concept pages and links. When something should not be there, say what else
would need removing with it.
Take undefined-ui/second-brain-privacy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.