Sets up a PARA-based second brain in any notes app (Notion, Obsidian, Apple Notes, Logseq) - Projects, Areas, Resources, Archives buckets, a frictionless universal capture inbox, weekly organizing, wiki-link and map-of-content linking, progressive summarization for recall, and maintenance rituals. Use when someone says "help me set up a second brain", "my notes are a mess and I can never find anything", "how do I organize Obsidian with PARA", or captures ideas but never uses them. Do NOT use for designing the underlying Notion database properties and relations - use notion-database instead - or for a task-management workflow - use gtd-system instead.
Click to play with sound.
---
name: Second Brain
description: Sets up a PARA-based second brain in any notes app (Notion, Obsidian, Apple Notes, Logseq) - Projects, Areas, Resources, Archives buckets, a frictionless universal capture inbox, weekly organizing, wiki-link and map-of-content linking, progressive summarization for recall, and maintenance rituals. Use when someone says "help me set up a second brain", "my notes are a mess and I can never find anything", "how do I organize Obsidian with PARA", or captures ideas but never uses them. Do NOT use for designing the underlying Notion database properties and relations - use notion-database instead - or for a task-management workflow - use gtd-system instead.
---
# Second Brain
A second brain is an external, trusted system for everything you want to remember
and act on. This skill sets one up using the PARA method in any notes app
(Notion, Obsidian, Apple Notes, Logseq).
## The PARA model
Organize every note into one of four top-level buckets, ordered by actionability:
- **Projects** - short-term efforts with a goal and a deadline (e.g. "Ship Q3 launch").
- **Areas** - ongoing responsibilities with a standard to maintain (e.g. "Health", "Finances").
- **Resources** - topics of interest for future reference (e.g. "Prompt engineering").
- **Archives** - inactive items from the other three buckets.
Rule: a note lives where you will next *act* on it, not where it topically "belongs".
## The four workflows
### 1. Capture… install to load the full skill