Skip to content
Back to skills

Second Brain Merge

ASecurity

Merge two pages that describe the same thing, preserving every distinct claim, redirecting inbound links, and recording the merge. Use this skill when the user approves a duplicate merge, says "these are the same page", "merge X into Y", or asks to clean up near-duplicates that a lint run proposed. Do NOT use to merge pages on your own judgement, to delete a page outright, or to split one page into several.

  • 809 stars
  • 0 votes
  • 0 copies
  • 2 views
  • 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-merge --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Second Brain Merge?

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

Security grade badge for Second Brain Merge
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/undefined-ui-second-brain-merge/badge)](https://www.skillsdirectory.com/skills/undefined-ui-second-brain-merge)

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-merge
description: >-
  Merge two pages that describe the same thing, preserving every distinct claim,
  redirecting inbound links, and recording the merge. Use this skill when the
  user approves a duplicate merge, says "these are the same page", "merge X into
  Y", or asks to clean up near-duplicates that a lint run proposed. Do NOT use
  to merge pages on your own judgement, to delete a page outright, or to split
  one page into several.
---

# Merge duplicate pages

A merge is irreversible in the way that matters: afterwards you cannot tell
which claim came from which page. Two ideas that look identical from their
summaries are often a general case and a specific one.

## Core rule

Never merge unprompted. Propose, wait for approval, then follow the procedure
exactly.

## Workflow

1. **Pick the survivor** by canonical name, not by which page is longer.
2. **Merge content.** Every distinct claim survives with its source. Overlapping
   claims collapse; differing ones both stay, following the contradiction rules.
3. **Merge aliases,** including the dead page's title as an alias on the
   survivor. This is what keeps old links and the user's memory working.
4. **Redirect inbound links** to the survivor. Check every backlink.
5. **Delete the old page,** or leave a stub only if it was linked from outside
   the vault.
6. **Record in `log.md`:** both names, the date, and why.

## Output format

```
Merged: [[old]] -> [[survivor]]
Claims kept from old page: <n>
Aliases added: <list>
Inbound links redirected: <n>
Conflicts recorded: <none | description>
```

## Calibration

If the two pages disagree about anything factual, that is a signal they may not
be duplicates. Surface the disagreement and ask before proceeding.

Never merge a page marked `maintained_by: human` into another without explicit
confirmation naming that page.

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.