second-brain-changed-my-mind

Solid

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.

AI & Automation 46 stars 7 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
70
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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.

Details

Author
undefined-ui
Repository
undefined-ui/second-brain-os
Created
3 days ago
Last Updated
today
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

flip-the-script

Use when about to assert a fact that has an exact external answer and the answer came from memory rather than a checked source — a library/API version or signature, a current-state or "latest/recommended" claim, an exact number/price/stat/date, a niche or long-tail detail, or a "yes that works / I already checked" you cannot point to evidence for. Also use whenever you notice felt-certainty standing in for a source, or you are about to declare something fixed/done/correct without a re-run. The move: treat unverified recall as stale + overconfident by default, classify whether the claim is in a reliable or unreliable recall domain, and route the unreliable ones to EXTERNAL ground truth (read-the-damn-docs, search, read the source, measure, or a fresh-context check) before asserting — not to internal second-guessing. Reach for it by default before any version/API/current-state/exact claim; skip it for stable well-known facts and settled, already-verified things (re-litigating those is its own failure mode).

0 Updated 3 days ago
88plug
AI & Automation Listed

query

Query Tracework's decision replay index for why a project chose a path, what alternatives were rejected, what should be revisited, what impact a decision had, or any natural-language question about project history. Use this skill for "/tracework:query", "why did we choose this?", "为什么当时这么选", "有没有被拒绝过的方案", "revisit this decision", "auth 迁移做到哪了", "我们讨论过 rate limiting 吗", or when a coding agent needs cited decision evidence before changing architecture, contracts, prompts, schemas, or product direction.

2 Updated 5 days ago
KKenny0
AI & Automation Listed

what-changed-in-search

Check what changed in search or answer engines recently, always fetched live and never answered from training data, then show what it means for this specific site in measured counts with a control check before blaming anything on it. Use this skill whenever the user asks to: - Understand a recent Google core update or algorithm change - Explain a traffic drop or spike - Check whether something the site shipped or an external update caused a metric to move Trigger even for casual requests like "what changed in search", "was there a core update", "did Google change something", "why did our traffic drop", "is this the algorithm or something we did".

0 Updated 1 months ago
vcxcvii