Source profileQuality 69/100

paperclipai/paperclip/skills/para-memory-files/SKILL.md

para-memory-files

Use a file-based PARA memory system to store, retrieve, and organize durable knowledge across sessions. Trigger on saving facts, daily notes, entity records, weekly synthesis, recall, tacit user patterns, or plan memory.

Source repository stars
74,938
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Persistent, file-based memory organized by Tiago Forte's PARA method. Three layers: a knowledge graph, daily notes, and tacit knowledge. All paths are relative to $AGENTHOME.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/paperclipai/paperclip --skill "skills/para-memory-files"
    Safe inspection promptEditorial

    Inspect the Agent Skill "para-memory-files" from https://github.com/paperclipai/paperclip/blob/77979950381a99271e4690c581a7440b73807b11/skills/para-memory-files/SKILL.md at commit 77979950381a99271e4690c581a7440b73807b11. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Three Memory Layers

      Entity-based storage. Each entity gets a folder with two tiers:

      summary.md -- quick context, load first.items.yaml -- atomic facts, load on demand.Projects -- active work with a goal or deadline. Move to archives when complete.
    2. 02

      Layer 1: Knowledge Graph ($AGENTHOME/life/ -- PARA)

      Entity-based storage. Each entity gets a folder with two tiers:

      summary.md -- quick context, load first.items.yaml -- atomic facts, load on demand.Projects -- active work with a goal or deadline. Move to archives when complete.
    3. 03

      Layer 2: Daily Notes ($AGENTHOME/memory/YYYY-MM-DD.md)

      Raw timeline of events -- the "when" layer.

      Write continuously during conversations.Extract durable facts to Layer 1 during heartbeats.Raw timeline of events -- the "when" layer.
    4. 04

      Layer 3: Tacit Knowledge ($AGENTHOME/MEMORY.md)

      How the user operates -- patterns, preferences, lessons learned.

      Not facts about the world; facts about the user.Update whenever you learn new operating patterns.How the user operates -- patterns, preferences, lessons learned.

    Permission review

    Static risk signals and limitations

    Writes files

    medium · line 70

    The documentation asks the agent to create, modify, or delete local files.

    Want to remember something -> WRITE IT TO A FILE.

    Writes files

    medium · line 92

    The documentation asks the agent to create, modify, or delete local files.

    Keep plans in timestamped files in `plans/` at the project root (outside personal memory so other agents can access them). Use `qmd` to search plans. Plans go stale -- if a newer plan exists, do not confuse yourself with an older version. I

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score69/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars74,938SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    paperclipai/paperclip
    Skill path
    skills/para-memory-files/SKILL.md
    Commit
    77979950381a99271e4690c581a7440b73807b11
    License
    MIT
    Collected
    2026-07-28
    Default branch
    master
    View the original SKILL.md

    PARA Memory Files

    Persistent, file-based memory organized by Tiago Forte's PARA method. Three layers: a knowledge graph, daily notes, and tacit knowledge. All paths are relative to $AGENT_HOME.

    Three Memory Layers

    Layer 1: Knowledge Graph ($AGENT_HOME/life/ -- PARA)

    Entity-based storage. Each entity gets a folder with two tiers:

    1. summary.md -- quick context, load first.
    2. items.yaml -- atomic facts, load on demand.
    $AGENT_HOME/life/
  projects/          # Active work with clear goals/deadlines
    <name>/
      summary.md
      items.yaml
  areas/             # Ongoing responsibilities, no end date
    people/<name>/
    companies/<name>/
  resources/         # Reference material, topics of interest
    <topic>/
  archives/          # Inactive items from the other three
  index.md

    PARA rules:

    • Projects -- active work with a goal or deadline. Move to archives when complete.
    • Areas -- ongoing (people, companies, responsibilities). No end date.
    • Resources -- reference material, topics of interest.
    • Archives -- inactive items from any category.

    Fact rules:

    • Save durable facts immediately to items.yaml.
    • Weekly: rewrite summary.md from active facts.
    • Never delete facts. Supersede instead (status: superseded, add superseded_by).
    • When an entity goes inactive, move its folder to $AGENT_HOME/life/archives/.

    When to create an entity:

    • Mentioned 3+ times, OR
    • Direct relationship to the user (family, coworker, partner, client), OR
    • Significant project or company in the user's life.
    • Otherwise, note it in daily notes.

    For the atomic fact YAML schema and memory decay rules, see references/schemas.md.

    Layer 2: Daily Notes ($AGENT_HOME/memory/YYYY-MM-DD.md)

    Raw timeline of events -- the "when" layer.

    • Write continuously during conversations.
    • Extract durable facts to Layer 1 during heartbeats.

    Layer 3: Tacit Knowledge ($AGENT_HOME/MEMORY.md)

    How the user operates -- patterns, preferences, lessons learned.

    • Not facts about the world; facts about the user.
    • Update whenever you learn new operating patterns.

    Write It Down -- No Mental Notes

    Memory does not survive session restarts. Files do.

    • Want to remember something -> WRITE IT TO A FILE.
    • "Remember this" -> update $AGENT_HOME/memory/YYYY-MM-DD.md or the relevant entity file.
    • Learn a lesson -> update AGENTS.md, TOOLS.md, or the relevant skill file.
    • Make a mistake -> document it so future-you does not repeat it.
    • On-disk text files are always better than holding it in temporary context.

    Memory Recall -- Use qmd

    Use qmd rather than grepping files:

    qmd query "what happened at Christmas"   # Semantic search with reranking
qmd search "specific phrase"              # BM25 keyword search
qmd vsearch "conceptual question"         # Pure vector similarity

    Index your personal folder: qmd index $AGENT_HOME

    Vectors + BM25 + reranking finds things even when the wording differs.

    Planning

    Keep plans in timestamped files in plans/ at the project root (outside personal memory so other agents can access them). Use qmd to search plans. Plans go stale -- if a newer plan exists, do not confuse yourself with an older version. If you notice staleness, update the file to note what it is supersededBy.