para-memory-files

Store and retrieve persistent knowledge across sessions using a file-based PARA system.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/VitorRibeiro45/paperclip --skill para-memory-files-vitorribeiro45
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: para-memory-files
Source: https://github.com/VitorRibeiro45/paperclip/tree/main/skills/para-memory-files
Command: npx skills add https://github.com/VitorRibeiro45/paperclip --skill para-memory-files-vitorribeiro45

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent, file-based memory organized by Tiago Forte's PARA method helps you store, retrieve, and organize knowledge across sessions, ensuring long-term context is preserved.

Core Features & Use Cases

  • Knowledge Graph Layer: entity-based storage under $AGENT_HOME/life/ with per-entity folders containing summary.md and items.yaml for durable facts.
  • Daily Notes Layer: raw timeline stored in $AGENT_HOME/memory/YYYY-MM-DD.md; extracts durable facts during heartbeats to Layer 1.
  • Tacit Knowledge Layer: stores user patterns and preferences in $AGENT_HOME/MEMORY.md for quick recall and improved automation.
  • Planning & Synthesis: supports weekly synthesis, archiving, and recall via qmd queries across memory layers.

Quick Start

Begin by saving your first durable fact to a new or existing entity under $AGENT_HOME/life and writing your first daily note to $AGENT_HOME/memory/YYYY-MM-DD.md.

Frequently Asked Questions about para-memory-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize persistent knowledge using the PARA method for long-term recall?

Persistent knowledge using the PARA method is organized by storing durable facts in a structured file-based hierarchy across projects, areas, resources, and archives, ensuring long-term context is preserved across sessions.

What's the best way to store daily notes and extract durable facts automatically?

Daily notes are stored as raw timelines in YYYY-MM-DD.md files, and the system automatically extracts durable facts during heartbeats into a knowledge graph layer for entity-based storage.

How does file-based memory management work with a knowledge graph?

File-based memory management works by implementing a layered memory model with an atomic fact store in items.yaml and per-entity folders containing summary.md, supporting recall via qmd queries.

Can I use qmd queries to recall knowledge across different memory layers?

Yes, you can use qmd queries to recall knowledge across memory layers, supporting weekly synthesis, archiving, and retrieval of tacit knowledge patterns stored in MEMORY.md.

Do I need a specific environment setup to implement a PARA knowledge base?

You need an environment supporting $AGENT_HOME to implement a PARA knowledge base, where the system creates per-entity folders under $AGENT_HOME/life/ and stores daily notes under $AGENT_HOME/memory/.

Why does memory decay matter when planning and recalling structured knowledge?

Memory decay rules matter because they govern planning and recall workflows by determining how durable facts are retained or archived over time, ensuring the knowledge base remains relevant and uncluttered.