Skip to content

undefined-ui/second-brain-os / skills/second-brain-chat-import

second-brain-chat-import

Unverified

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.

Import chat history

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.

Core rule

Privacy pass before triage, triage before ingestion. Never ingest an export wholesale.

Workflow

  1. Convert with scripts/chat_export_to_md.py into one file per conversation, filtering out short exchanges.
  2. Privacy pass. List conversations touching health, money, other people's private information, or confidential work. The user decides; you delete nothing on your own.
  3. Triage the rest into three piles: worth ingesting (they worked something out, decided something, or got an explanation that landed), worth archiving in raw/, and delete.
  4. Report the lists. Move nothing yet.
  5. On approval, ingest the first pile, with the instruction that these are the user's own thinking: build pages around what they were working out and what they concluded, not around the assistant's explanations.

Output format

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>

Calibration

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.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall