second-brain-changed-my-mind
SolidTrace 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.
Install
Quality Score: 81/100
Skill Content
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
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).
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.
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".