Skip to content

undefined-ui/second-brain-os / skills/second-brain-changed-my-mind

second-brain-changed-my-mind

Unverified

Trace where the user's recorded position on something has shifted: superseded claims, contradictions between sources of different dates, and what evidence moved them. Use this skill when the user asks what they have changed their mind about, how their thinking on a topic developed, what they used to believe, or wants a quarterly look back at their own positions. Do NOT use for finding contradictions between sources with no time dimension, or for a current-state answer.

Trace changed positions

This is the query a vault can answer that nothing else can, and the reason the supersession rules exist. It only works because contradictions are recorded rather than overwritten.

Core rule

Report the change with both positions, both dates and the evidence between them. A conclusion without its history is just the current claim.

Workflow

  1. Find superseded claims across concept pages, and contradictions where the sources differ in date.
  2. Reconstruct the sequence: what the page said, when, based on what; what changed it, when.
  3. Distinguish real revision from correction. A factual error being fixed is not a change of mind. A conclusion being revised on better evidence is.
  4. Flag unresolved ones. Contradictions still sitting open are the most actionable output here.
  5. Say how firm the current position is, based on what moved it.

Output format

## <topic>
Was: <claim> (<source>, <date>)
Now: <claim> (<source>, <date>)
What moved it: <evidence>
Firmness: <what would move it again>

## Still unresolved
<contradictions with no current position>

Calibration

If nothing has changed in the period, say so in one line. Manufacturing an apparent revision from two pages that never disagreed is worse than an empty result.

Never present the more recent source as correct by virtue of being recent.

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