>- Triage an exported chat history into what to ingest, what to archive and what to delete, with a privacy pass first. Use this skill when the user has exported their Claude or ChatGPT history, asks to import old conversations, or asks what in their chat archive is worth keeping. Do NOT use for ingesting a single pasted conversation, or for any material the user has not explicitly asked to bring into the vault.
npx skills add https://github.com/undefined-ui/second-brain-os --skill second-brain-chat-import
Chat history is the most underrated source a person owns and the most sensitive.
It records their reasoning, not just facts, and it also records things they would
not want in a file that gets synced, committed and backed up.
Privacy pass before triage, triage before ingestion. Never ingest an export
wholesale.
scripts/chat_export_to_md.py into one file perconversation, filtering out short exchanges.
private information, or confidential work. The user decides; you delete
nothing on your own.
out, decided something, or got an explanation that landed), worth archiving
in raw/, and delete.
the user's own thinking: build pages around what they were working out and
what they concluded, not around the assistant's explanations.
Converted: <n> conversations (<n> skipped as too short)
Privacy review needed: <n>
<title> - <why>
Worth ingesting: <n>
<title> - <what it worked out>
Archive only: <n>
Delete suggested: <n>
Expect roughly nine in ten conversations to be throwaway lookups. A triage that
recommends ingesting most of the export has not filtered.
Record dates on every page. A position from two years ago is not a current
belief, and the vault has to be able to tell the difference.
Take undefined-ui/second-brain-chat-import 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.