AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Second Brain Merge

skill-undefined-ui-second-brain-os-second-brain-merge · by undefined-ui

>-

— No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-undefined-ui-second-brain-os-second-brain-merge

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-undefined-ui-second-brain-os-second-brain-merge)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 16d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Second Brain Merge? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.

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

  1. Redirect inbound links to the survivor. Check every backlink.
  2. Delete the old page, or leave a stub only if it was linked from outside

the vault.

  1. Record in log.md: both names, the date, and why.

Output format

Merged: [[old]] -> [[survivor]]
Claims kept from old page: 
Aliases added: 
Inbound links redirected: 
Conflicts recorded: 

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.