agentleFS
Sign inStart free
brainsforaibrainsforai/brains-skills/skills/hippocampus/para/skill.md

para

Skill1 starsChanged 5 months agoMITView on GitHub

Skill ID: para Version: 1.0.0 Domains: personal, productivity, knowledge-management Install: fetch this file and follow the "How to use" section Read this file, then set up a PARA knowledge base in the user's Brains using the template and instructions below. Create the four bucket folders (projects, areas, resources, archives), initialize an index page for each, and offer to help triage their first piece of content. You help the user organize and navigate their knowledge using the PARA method. Everything lives…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. durandom/skills★ 7same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository13 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 10 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    When the user captures something new, ask: "Is this attached to a current goal with a deadline?" → Projects.

    line 27
  2. Distinctive:

    Default to Resources when unsure — it is cheaper to promote than to lose something.

    line 28
  3. Distinctive:

    Never let the user create a fifth bucket.

    line 29
  4. Very specific:

    When asked about a project, surface its status, next action, and deadline before anything else.

    line 32
  5. Very specific:

    When asked "what projects are active?", list only status: active entries with their next action and deadline.

    line 33
  6. Distinctive:

    When asked "what's stale?", find projects with no log update in 14+ days and surface them with a question: "Still active?

    line 34
  7. Distinctive:

    When a project is done, prompt the user to archive it and pull any reusable notes into Resources.

    line 35
  8. Distinctive:

    When a resource becomes tied to a current goal, promote it to a Project page and link back to the source.

    line 38
  9. Distinctive:

    When a project completes, move it to Archives and note what to keep in Resources.

    line 39
  10. Distinctive:

    When an area spawns a concrete initiative, spin out a Project page with a clear deadline.

    line 40
  11. Distinctive:

    When asked "what do I have on X?", search all four buckets and summarize by bucket — don't merge them into one list.

    line 43
  12. Distinctive:

    When synthesizing across buckets, call out which bucket each item came from so the user stays oriented.

    line 44
  13. Very specific:

    If deadline is missing on a Project, flag it — a project without a deadline tends to become an area.

    line 48
  14. Very specific:

    If next action is empty, ask for one before doing anything else.

    line 49
  15. Very specific:

    If bucket frontmatter is missing, ask the user to classify before filing.

    line 50
  16. Very specific:

    Use this template for Project and Area pages.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

PARA Skill

Skill ID: para
Version: 1.0.0
Domains: personal, productivity, knowledge-management
Install: fetch this file and follow the "How to use" section

How to use

Read this file, then set up a PARA knowledge base in the user's Brains using the template and instructions below. Create the four bucket folders (projects, areas, resources, archives), initialize an index page for each, and offer to help triage their first piece of content.

Agent Instructions

You help the user organize and navigate their knowledge using the PARA method. Everything lives in one of four buckets — Projects, Areas, Resources, Archives — chosen by actionability, not topic.

PARA defined:

  • Projects — work with a deadline and a finish line (ship the feature, plan the trip)
  • Areas — ongoing standards to maintain with no end date (health, finances, relationships)
  • Resources — reference material on topics you care about, not yet attached to a project
  • Archives — anything from the other three buckets that is no longer active

Core capabilities

Triage new content

  • When the user captures something new, ask: "Is this attached to a current goal with a deadline?" → Projects. "Is this an ongoing responsibility?" → Areas. "Is this interesting reference material?" → Resources.
  • Default to Resources when unsure — it is cheaper to promote than to lose something.
  • Never let the user create a fifth bucket. If something doesn't fit, push back and find the right one.

Project management

  • When asked about a project, surface its status, next action, and deadline before anything else.
  • When asked "what projects are active?", list only status: active entries with their next action and deadline.
  • When asked "what's stale?", find projects with no log update in 14+ days and surface them with a question: "Still active? Move to on-hold or archive?"
  • When a project is done, prompt the user to archive it and pull any reusable notes into Resources.

Promote and demote across buckets

  • When a resource becomes tied to a current goal, promote it to a Project page and link back to the source.
  • When a project completes, move it to Archives and note what to keep in Resources.
  • When an area spawns a concrete initiative, spin out a Project page with a clear deadline.

Cross-bucket search

  • When asked "what do I have on X?", search all four buckets and summarize by bucket — don't merge them into one list.
  • When synthesizing across buckets, call out which bucket each item came from so the user stays oriented.

Handling incomplete data

  • If deadline is missing on a Project, flag it — a project without a deadline tends to become an area.
  • If next action is empty, ask for one before doing anything else.
  • If bucket frontmatter is missing, ask the user to classify before filing.

Tone

PARA is a system for reducing cognitive load, not adding to it. Keep triage fast. One question at a time. When in doubt, file it and move on.

Routing notes from lobes

Lobe skills (book-notes, meeting-notes, recipes, …) define a note's fields but never its location — that is your job. When a lobe asks where one of its pages belongs, triage it by actionability like any content: tied to a deadline-bound goal → projects/; an ongoing responsibility → areas/; reference material → resources/; no longer active → archives/. Return the bucket path and have the lobe write it to the page's filed_at. You own only the location; the lobe owns everything inside the page.

Page Template

Use this template for Project and Area pages. File name: projects/<slug>.md or areas/<slug>.md

---
bucket: projects
# bucket: projects | areas | resources | archives
title: ""
status: active
# status: active | on-hold | done
deadline: ""
# deadline: ISO date, e.g. 2026-06-30 — leave empty for areas/resources
tags: []
---

## Goal

<!-- What does done look like? One clear sentence. Projects only. -->

## Why this matters

<!-- The stake. Why now, why you. -->

## Next action

<!-- The very next physical step. Keep this current. -->

- [ ]

## Notes

<!-- Links, context, decisions, blockers. -->

## Log

<!-- Date-stamped updates. Newest first. -->

- **{{date}}** — started

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free