How do I install the Para System skill?

Run npx skillmds@latest add aroyburman-codes/para-system in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Para System skill do?

PARA Second Brain System It is listed under Coding & Dev Tools on SkillMD.

Is Para System safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Para System?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Para System free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Para System?

aroyburman-codes (@aroyburman-codes) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Para System by aroyburman-codes — Agent Skill

Name: Para System
Author: aroyburman-codes

File contents

PARA Second Brain System

You have access to the PARA (Projects/Areas/Resources/Archive) methodology for organizing work and knowledge.

When This Skill Activates

Activate when the user:

Mentions PARA, "second brain", or "where should I put this"
Asks about organizing their work, notes, or knowledge
Wants to decide between Projects, Areas, Resources, or Archive
Asks about review cadence or PARA hygiene

Core PARA Concepts

Projects = Goal + Deadline. Bounded efforts with a clear finish line. Areas = Ongoing Responsibility. No end date — standards to maintain. Resources = Reference Material. Things to find later, no action required now. Archive = Inactive Items. Done, paused, or deprecated — not deleted, just shelved.

Quick Decision Tree

Has a clear end goal + deadline? → Projects
Ongoing responsibility to maintain? → Areas
Reference material for later? → Resources
Done or no longer relevant? → Archive
None of the above? → Don't capture it.

Key Rules

8-10 active projects max. More means you're spread too thin.
Archive aggressively. Clutter has real cognitive cost. Archiving is free.
Capture fast, organize later. Don't agonize over categories — the weekly review is when you sort things out.
Every item needs a filled-in context.md. Empty templates are noise.
Cross-reference related items. Projects often connect to Areas and Resources.

Available Commands

/para-setup [path] — Initialize a PARA directory structure
/para-add <category> <name> — Add a new item to any category
/para-review [weekly|monthly] — Walk through your system and update statuses
/para-capture [text] — Quick-capture a note from the current conversation
/para-status [category] — See an overview of your PARA system

Review Cadence

Weekly (30 min): Scan projects, check areas, capture and archive
Monthly (60 min): Weekly + strategic alignment + resource refresh
Quarterly (90 min): Monthly + growth review + system health check

Reference Files

For detailed templates, see references/templates.md. For organization patterns and workflow guidance, see references/patterns.md.

---name: para-systemdescription: PARA Second Brain System---# PARA Second Brain SystemYou have access to the PARA (Projects/Areas/Resources/Archive) methodology for organizing work and knowledge.## When This Skill ActivatesActivate when the user:- Mentions PARA, "second brain", or "where should I put this"- Asks about organizing their work, notes, or knowledge- Wants to decide between Projects, Areas, Resources, or Archive- Asks about review cadence or PARA hygiene## Core PARA Concepts**Projects** = Goal + Deadline. Bounded efforts with a clear finish line.**Areas** = Ongoing Responsibility. No end date — standards to maintain.**Resources** = Reference Material. Things to find later, no action required now.**Archive** = Inactive Items. Done, paused, or deprecated — not deleted, just shelved.## Quick Decision Tree```Has a clear end goal + deadline? → ProjectsOngoing responsibility to maintain? → AreasReference material for later? → ResourcesDone or no longer relevant? → ArchiveNone of the above? → Don't capture it.```## Key Rules- **8-10 active projects max.** More means you're spread too thin.- **Archive aggressively.** Clutter has real cognitive cost. Archiving is free.- **Capture fast, organize later.** Don't agonize over categories — the weekly review is when you sort things out.- **Every item needs a filled-in context.md.** Empty templates are noise.- **Cross-reference related items.** Projects often connect to Areas and Resources.## Available Commands- `/para-setup [path]` — Initialize a PARA directory structure- `/para-add <category> <name>` — Add a new item to any category- `/para-review [weekly|monthly]` — Walk through your system and update statuses- `/para-capture [text]` — Quick-capture a note from the current conversation- `/para-status [category]` — See an overview of your PARA system## Review Cadence- **Weekly (30 min):** Scan projects, check areas, capture and archive- **Monthly (60 min):** Weekly + strategic alignment + resource refresh- **Quarterly (90 min):** Monthly + growth review + system health check## Reference FilesFor detailed templates, see `references/templates.md`.For organization patterns and workflow guidance, see `references/patterns.md`.

Frequently asked questions

Para System