Skip to content
Back to skills

Second Brain Changed My Mind

ASecurity

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.

  • 809 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 19, 2026
ai-agents

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add undefined-ui/second-brain-os --skill second-brain-changed-my-mind --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Second Brain Changed My Mind?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Second Brain Changed My Mind
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/undefined-ui-second-brain-changed-my-mind/badge)](https://www.skillsdirectory.com/skills/undefined-ui-second-brain-changed-my-mind)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: second-brain-changed-my-mind
description: >-
  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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.