para-memory-files

Organize persistent user knowledge into PARA layers with atomic facts in items.yaml.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Avishai-Tsabari/agents_manager --skill para-memory-files-avishai-tsabari
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: para-memory-files
Source: https://github.com/Avishai-Tsabari/agents_manager/tree/main/skills/para-memory-files
Command: npx skills add https://github.com/Avishai-Tsabari/agents_manager --skill para-memory-files-avishai-tsabari

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Persistent, file-based memory organized by Tiago Forte's PARA method to ensure durable facts, structured notes, and reliable recall across sessions.

Core Features & Use Cases

  • PARA layers: knowledge graph with entities, daily notes timeline, and tacit knowledge store
  • Atomic facts: items.yaml as the primary durable facts store, summaries rewritten weekly
  • Planning and recall: weekly synthesis, decay rules, and reactivation via recall

Quick Start

Create your first PARA entity by saving a durable fact to the knowledge graph under $AGENT_HOME/life.

Frequently Asked Questions about para-memory-files

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

FAQPage Schema
How does PARA memory work for organizing knowledge across sessions?

PARA method organizes knowledge into Projects, Areas, Resources, and Archives layers to ensure durable facts and reliable recall across sessions. This Skill structures notes and entities within that framework, storing atomic facts in items.yaml for persistence.

How do I save daily notes and project entities using a PARA knowledge graph?

Create entity folders for projects and save durable facts to the knowledge graph under your AGENT_HOME/life directory. The system structures these as atomic facts in items.yaml, building a daily notes timeline and tacit knowledge store automatically.

What is the best way to persist tacit user patterns and knowledge for recall?

Using a file-based memory system with weekly synthesis is the best way to persist tacit user patterns. It stores tacit knowledge in structured layers, applying decay rules and scheduling reactivation via recall to maintain relevant context.

Can I use file-based memory for weekly synthesis and knowledge management without external dependencies?

Yes, this file-based knowledge management approach operates without external dependencies. It relies entirely on local YAML files to implement atomic fact storage, layered memory, and weekly synthesis with decay and recall rules.

Why does memory recall need decay rules in a knowledge management system?

Decay rules prevent knowledge overload by aging out less relevant facts over time. The weekly synthesis process uses these rules to prioritize which durable facts and tacit patterns get reactivated during recall, keeping memory efficient.