mcpField
P
para-second-brain

para-second-brain

github.com/robdefeoProductivity4407 installsUpdated 19w ago
Repository

About para-second-brain

A PARA-based skill for organizing and maintaining a second brain. It routes classification, workflow, example, and troubleshooting questions to focused references, and can validate a structure with a script.

Key features

  1. 01PARA classification guidance
  2. 02Intent-based reference routing
  3. 03Inbox, review, and archive workflows
  4. 04Structure validation and reports

Use cases

  1. 01Deciding where an item belongs
  2. 02Setting up or reviewing a PARA workflow
  3. 03Checking second-brain structure health
  4. 04Troubleshooting organization issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/robdefeo/agent-skills --skill para-second-brain

After installing, type/para-second-brainin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
common-problems.md
decision-trees.md
examples.md
workflows.md
scripts/
validate.sh
tests/fixture-second-brain/00_INBOX/
inbox-note.md
tests/fixture-second-brain/10_PROJECTS/Active/Hiring Sprint/
AGENTS.md
tests/fixture-second-brain/10_PROJECTS/Active/Q2 Campaign/
AGENTS.md
Notes.md
tests/fixture-second-brain/10_PROJECTS/Completed/Website Redesign/
AGENTS.md
tests/fixture-second-brain/10_PROJECTS/On Hold/
.gitkeep
tests/fixture-second-brain/20_AREAS/
Q2 Campaign handoff.md
tests/fixture-second-brain/20_AREAS/People Management/
notes.md
tests/fixture-second-brain/30_RESOURCES/Engineering/
api-guidelines.md
tests/fixture-second-brain/40_ARCHIVE/Areas/
.gitkeep
tests/fixture-second-brain/40_ARCHIVE/Projects/
.gitkeep
tests/fixture-second-brain/40_ARCHIVE/Resources/
.gitkeep

Details

From the project README

PARA Method

Use this skill to help users organize and maintain a second brain using the PARA system (Projects, Areas, Resources, Archives).

Routing

Pick the entry point based on user intent:

  • Classification and "where does this go?" questions: read references/decision-trees.md
  • Example requests and edge-case comparisons: read references/examples.md
  • Operational process requests (inbox, review, setup, close-out, archive): read references/workflows.md
  • Troubleshooting pain points and validation guidance: read references/common-problems.md

If the request is broad or does not clearly match one route, default to references/decision-trees.md.

Output Convention

  • Classification guidance and Q&A: answer in chat
  • Validation workflows: run scripts/validate.sh and write report output to PARA-validation-YYYY-MM-DD.md in the current working directory
  • Installation location: out of scope for this skill; installation is handled by separate tooling

Terminology

  • Use "second brain" for the user's vault/folder structure
  • Use "PARA system" only for the method/framework

Validation Workflow

When the user asks to validate structure or project health:

  1. Read references/common-problems.md for interpretation guidance.
  2. Run scripts/validate.sh <path> (or omit path to use current directory).
  3. Save report output to PARA-validation-YYYY-MM-DD.md if user wants a file.
  4. Summarize critical findings and recommended next actions.

Comments

Markdown supported