para-memory-files

Organize and persist knowledge across sessions using the PARA memory model.

Updated Apr 6, 2026

Search Tags:#planning #recall #memory #knowledge-management #para #qmd

Ready to run

npx skills add https://github.com/jkeith10/operatorOS --skill para-memory-files-jkeith10

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: para-memory-files
Source: https://github.com/jkeith10/operatorOS/tree/main/skills/para-memory-files
Command: npx skills add https://github.com/jkeith10/operatorOS --skill para-memory-files-jkeith10

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Persistent, structured memory across sessions using Tiago Forte's PARA method, enabling you to store, retrieve, and update knowledge over time.

Core Features & Use Cases

Layered memory model with a knowledge graph (life/ with summary.md and items.yaml), daily notes (memory/YYYY-MM-DD.md), and tacit knowledge (MEMORY.md).
Strong memory governance: never delete facts, layer aging via decay, and archival workflows for inactive items.
Fast recall and planning: weekly synthesis, cross-session context recall, and planning artifacts accessible via qmd.

Quick Start

Create a new daily note for today and save any new durable facts to the PARA knowledge graph under the appropriate entity.

Frequently Asked Questions about para-memory-files

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

FAQPage Schema

How do I maintain persistent agent memory across different sessions?▼

To maintain persistent memory across sessions, you can use a PARA memory model that organizes knowledge into projects, areas, resources, and archives, storing durable facts in a knowledge graph and daily notes for later recall.

What is the PARA method for personal knowledge management?▼

The PARA method for knowledge management organizes information into projects, areas, resources, and archives. It enables personal agents to store, retrieve, and update structured knowledge over time using a layered memory system.

How do I organize cross-session context for long-term planning?▼

You organize cross-session context by applying a three-layer memory system: a knowledge graph for entities, daily notes for records, and tacit knowledge. This supports long-term recall and planning across projects.

Can I retrieve archived knowledge and daily notes using qmd?▼

Yes, you can retrieve archived knowledge and daily notes using qmd. The system provides fast recall and planning access, pulling cross-session context and weekly synthesis artifacts directly through qmd queries.

How does memory decay work when managing long-term knowledge?▼

Memory decay manages long-term knowledge by layering aging workflows over inactive items instead of deleting facts. This archival governance ensures outdated context fades appropriately while preserving durable facts.

Does this knowledge management approach require deleting outdated facts?▼

No, this knowledge management approach never deletes facts. It enforces strong memory governance by layering aging via decay and using archival workflows to handle inactive items in the knowledge graph.