Skip to content
Skills Library
Personal productivity · Planning

second-brain

/second-brain

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 - o

Repository
skills ↗
Licence
MIT
Last repository change
13.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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 - o

Triggers from the description

help me set up a second brainmy notes are a mess and I can never find anythinghow do I organize Obsidian with PARA
Original author 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 - o

How it works

  1. The PARA model
  2. The four workflows
  3. Note template
  4. Maintenance rituals
  5. Anti-patterns to avoid
  6. Quality bar
  7. Deliverable
Original SKILL.md headings · 97 lines, 539 words
SKILL.md preview
---
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.
metadata:
  title: "Second Brain"
---

# 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

Lower friction to near zero. Set up one universal inbox note or quick-capture
shortcut. Capture anything: ideas, links, quotes, tasks. Do NOT organize at capture
time - speed beats structure here.

### 2. Organize (weekly)

Once a week, empty the inbox. For each item:
- Is it actionable now? -> attach to a **Project**.
- Is it an ongoing standard? -> file under an **Area**.
- Might it be useful later? -> **Resource**.
- Otherwise -> delete or **Archive**.

### 3. Link

Connect notes so recall works by association, not folders:
- Add 2-3 `[[wiki-links]]` or relations to related notes when you file something.
- Maintain a few **index/MOC** (map of content) notes that link out to clusters.
- Tag sparingly - links beat tags for retrieval.

### 4. Recall (Express)

The point of the system is output. When starting work:
- Search the relevant Project/Area note first.
- Follow links outward to gather supporting Resources.
- Distill into a working draft. Progressive summarization: bold the best lines,
  highlight the best of the bold.

## Note template

```
# <Title>
Bucket: Projects | Areas | Resources | Archives
Created: <date>
Links: [[related-1]] [[related-2]]

## Summary
<2-3 sentence why-this-matters>

## Notes
<content>

## Next action
<the single next step, if any>
```

## Maintenance rituals

- **Weekly review (20 min):** empty inbox, mark finished projects, archive the dead.
- **Monthly (10 min):** promote hot Resources, prune stale links.

## Anti-patterns to avoid

- Over-tagging or building deep folder trees - PARA stays flat (4 levels max).
- Collecting without expressing - capture is only valuable if you later create.
- Organizing at capture time - it kills capture velocity.

## Quality bar

- Capturing a new thought takes seconds and zero decisions - one inbox, no
  filing at capture time.
- Every existing note lands in exactly one PARA bucket, placed by next action,
  not by topic.
- Filed notes carry 2-3 outbound links, and each major cluster has an MOC note
  pointing into it.
- The weekly and monthly rituals are written down with a trigger (day + time),
  not left as intentions.

## Deliverable

Produce a working second-brain setup in the user's chosen app: the four PARA
top-level buckets created, a universal capture inbox wired to a quick-capture
entry point, the note template installed, 2-3 starter MOC/index notes for their
main clusters, and a written maintenance checklist (the 20-minute weekly review
and 10-minute monthly prune) with a scheduled trigger for each.

Versions

RepositoryScoreLicence
This page · SkillMedev/skills100MIT
coreyhaines31/makerskills100MIT
DaraBoth/skilljmskill100MIT
Malek1414/steroid-claude100MIT
stancsz/second-brain100MIT
owlinthebarnai/second-brain-kit90MIT

Database snapshot: 13.11.2026 · package version 5725458ecf67 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100wiki-personal
    Use when discussing personal productivity systems, second-brain methodologies, note-taking tools, or knowledge management approaches for legal professionals. Covers the PARA method, Obsidian for linked-knowledge management, Notion for structured knowledge, and Apple Notes for…
  • 100building-second-brain-pkm-for-developers
    Use this skill when organizing developer knowledge, project archives, code snippets, and career assets into an actionable Second Brain (PARA).
  • 100obsidian-vault-structure-para-method
    Use this skill when organizing an Obsidian vault into actionable Projects, long-term Areas, reference Resources, and inactive Archives.
  • 100para-organizer
    Sorts notes and folders into Projects, Areas, Resources, and Archives, and proposes a move plan they approve before anything changes. Use when someone mentions PARA or a second brain, wants to reorganize a messy notes app, has too many folders, does not know where a note…
  • 100obsidian-brain
    Autonomous Obsidian vault management using the PARA + LLM Wiki pattern. Three operations: ingest (inbox to wiki + PARA routing), query (cross-vault synthesis), lint (health check). Scheduled via CronCreate 4x/day. Filesystem-only -- no Obsidian app dependency. Activate when the…
  • 1003d-brain
    Use when someone asks to build a 3D brain, visualize their AIOS or second brain, turn their knowledge into an interactive graph, or run /3d-brain or /3D brain.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.