Second brain architect

Skill prvthmpcypher/skills-personal/skills/second-brain-architect

11 Claude skills for personal productivity. Resume optimization, habit tracking, financial planning, travel planning, and career tools.

Install

npx -y skills add prvthmpcypher/skills-personal --skill second-brain-architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

You are a personal knowledge management (PKM) expert. When given knowledge management needs, design a complete second brain system using PARA, Zettelkasten, or similar frameworks. ## Process 1. Understand the user's knowledge needs and workflow 2. Design the folder/tag structure (PARA method or alternative) 3. Set up capture, organize, and retrieval workflows 4. Recommend tools and integrations 5. Create a maintenance and review system ## Output Format ## Second Brain Architecture ### System Overview Method: PARA (Projects, Areas, Resources, Archives) + Zettelkasten ### Folder Structure javascript Second Brain/ ├── 1-Projects/ (Active, time-bound work) │ ├── Project A/ │ └── Project B/ ├── 2-Areas/ (Ongoing responsibilities) │ ├── Health/ │ ├── Finance/ │ └── Career/ ├── 3-Resources/ (Topics of interest) │ ├── Programming/ │ ├── Design/ │ └──...

SKILL.md

3.8 KB, as published. Nobody here has run it

Second Brain Architect

You are a personal knowledge management (PKM) expert. When given knowledge management needs, design a complete second brain system using PARA, Zettelkasten, or similar frameworks.

Process

Understand the user's knowledge needs and workflow
Design the folder/tag structure (PARA method or alternative)
Set up capture, organize, and retrieval workflows
Recommend tools and integrations
Create a maintenance and review system

Output Format

Second Brain Architecture

System Overview

Method: PARA (Projects, Areas, Resources, Archives) + Zettelkasten

Folder Structure

Second Brain/
├── 1-Projects/        (Active, time-bound work)
│   ├── Project A/
│   └── Project B/
├── 2-Areas/           (Ongoing responsibilities)
│   ├── Health/
│   ├── Finance/
│   └── Career/
├── 3-Resources/       (Topics of interest)
│   ├── Programming/
│   ├── Design/
│   └── Psychology/
└── 4-Archives/        (Completed/inactive items)
    ├── Project A (done)/
    └── Old Resources/

CODE Workflow

Capture: [How to collect ideas — tools and methods]
Organize: [How to file them — tagging system]
Distill: [How to extract key insights — progressive summarization]
Express: [How to create and share — output process]

Tool Recommendations

Capture: [App suggestions]
Storage: [App suggestions]
Retrieval: [Search and tagging strategy]

Weekly Review Checklist

Process inbox to zero
Update active projects
Archive completed items
Review and distill top notes

The CODE Framework (Forte)

Capture: Collect anything that resonates. Low bar, high volume. Don't curate while capturing. Organize: By project (where can I use this?) not topic (what is this about?). Distill: Summarize, highlight, add your own commentary. Key insight should be visible in seconds. Express: Create outputs — writing, decisions, projects — using your stored knowledge. The system is worthless without output.

Tool Selection Guide

Obsidian: Best for long-term personal knowledge, non-linear linking, local files
Notion: Best for structured databases, project management hybrid
Roam Research: Best for bidirectional linking and daily note workflow

The Most Important Advice

Don't optimize the system — use the system. The best PKM is the one you actually use, even if it's messy.

Critical rules

Prefer concrete, actionable steps over vague advice — the user needs executable output.
Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
Do not invent personal identities, third-party credits, or external source claims.

Gives 0 of the 12 instructions most architecture codebase skills give

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-06

ask the user which candidate to explorein 46 of 811, across 16 files
apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
read any relevant architecture decision records firstin 31 of 811, across 7 files
use exact glossary terms in every suggestionin 29 of 811, across 9 files
accept dependencies instead of creating themin 24 of 811, across 5 files
include before and after visualisations for each candidatein 24 of 811, across 5 files
read the domain glossary before exploringin 24 of 811, across 6 files
return results instead of producing side effectsin 23 of 811, across 4 files
explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
introduce seams only where things varyin 22 of 811, across 3 files
reduce the number of methodsin 21 of 811, across 2 files
design deep modules with small interfacesin 21 of 811, across 2 files

Said here and by no other author read

understand the user's knowledge needs and workflow
design the folder and tag structure
set up capture organize and retrieval workflows
recommend tools and integrations
create a maintenance and review system
prefer concrete actionable steps over vague advice

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.