para-memory-files

Organize user memory in PARA folders with YAML-backed atomic facts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PARA Memory Files provides a structured, durable memory system that persists across sessions using a PARA-based folder hierarchy, enabling reliable recall and planning.

Core Features & Use Cases

  • Knowledge graph in PARA folders with two-tier facts (summary.md and items.yaml) for fast load and durable memory.
  • Daily notes as raw timeline for event tracking and heartbeats to extract facts.
  • Tacit knowledge layer for user patterns and operational lessons, updated from interactions.
  • Weekly synthesis and recall workflows via qmd for efficient context retrieval.

Quick Start

Create the PARA memory root at $AGENT_HOME and begin saving entities and daily notes using the two-tier fact files.

Frequently Asked Questions about para-memory-files

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

FAQPage Schema
How do I persist agent memory and facts across sessions using a PARA folder structure?

PARA knowledge management organizes durable memory into two-tier fact files: a summary.md for fast loading and an items.yaml for structured atomic facts. This enables reliable recall and planning across sessions.

How do I organize daily notes and extract facts for a knowledge management workflow?

Daily notes act as a raw timeline for event tracking, using heartbeats to extract durable facts. These facts are then saved into the PARA folder hierarchy for future synthesis and recall.

What is the best way to enforce non-deletion rules for knowledge management facts?

Enforcing non-deletion rules for knowledge management facts requires a structured memory system that persists YAML-backed atomic facts in a durable folder hierarchy, preventing data loss across sessions.

Can I use qmd-based search for weekly synthesis and context retrieval?

Yes, you can use qmd-based search to perform weekly synthesis and recall workflows. This enables efficient context retrieval from your stored knowledge graph and tacit knowledge layers.

Does plan-based memory planning work with tacit knowledge patterns?

Plan-based memory planning works alongside a tacit knowledge layer that captures user patterns and operational lessons. It updates these patterns directly from interactions to inform future planning.

What are the limitations of using YAML-backed atomic facts for knowledge management?

YAML-backed atomic facts require strict adherence to non-deletion rules and a structured PARA folder hierarchy. Limitations include the need for consistent heartbeat extraction and manual management of the two-tier summary and items files.