AgentStack
SKILL verified MIT Self-run

Para System

skill-aroyburman-codes-para-second-brain-para-system · by aroyburman-codes

A Claude skill from aroyburman-codes/para-second-brain.

No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-aroyburman-codes-para-second-brain-para-system

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Para System? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 — 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.