para-memory-files

Organize knowledge into PARA folders with atomic YAML facts and qmd queries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File-based memory system using Tiago Forte's PARA method. Use this skill whenever you need to store, retrieve, update, or organize knowledge across sessions. Covers three memory layers: (1) Knowledge graph in PARA folders with atomic YAML facts, (2) Daily notes as raw timeline, (3) Tacit knowledge about user patterns. Also handles planning files, memory decay, weekly synthesis, and recall via qmd. Trigger on any memory operation: saving facts, writing daily notes, creating entities, running weekly synthesis, recalling past context, or managing plans.

Core Features & Use Cases

  • Knowledge Graph Layer: Entity-based storage with per-entity folders containing summary.md (quick context) and items.yaml (atomic facts).
  • Daily Notes Layer: Raw timeline stored in memory/YYYY-MM-DD.md for a continuous, auditable history.
  • Tacit Knowledge Layer: Tracks user patterns, preferences, and lessons learned for improved interactions.
  • Planning and Recall: Supports planning files, weekly synthesis, and recall via qmd queries to surface relevant context.
  • Rules & Governance: Durable facts are never deleted; supersede older facts; inactive entities moved to life/archives.
  • Use Case: A designer uses PARA memory to organize projects, ideas, and contacts across multiple sessions and devices.

Quick Start

Create a new entity under life/projects and populate its summary.md and items.yaml to begin tracking durable facts.

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 personal knowledge and memories across sessions using the PARA method?

Organize personal knowledge across sessions using the PARA method by structuring information into Projects, Areas, Resources, and Archives folders. The system stores durable facts as atomic YAML items and contextual summaries, ensuring long-running personal knowledge management and recall.

How do I store durable facts and retrieve context for weekly synthesis in a knowledge graph?

Store durable facts as atomic YAML items in per-entity folders and retrieve context using qmd queries. The system supports weekly synthesis by reading contextual summaries and raw daily notes, enforcing versioning and decay rules to maintain an auditable knowledge graph.

What is the best way to maintain daily notes and a continuous timeline for personal knowledge management?

Maintain daily notes and a continuous timeline by saving raw entries to memory/YYYY-MM-DD.md files. This creates an auditable historical layer that complements the structured PARA knowledge graph and tacit knowledge layers for comprehensive personal knowledge management.

Can I use YAML and markdown files to manage long-running project planning and memory decay?

Yes, you can manage long-running project planning and memory decay using YAML files for atomic facts and markdown files for summaries. The system applies decay rules, moving inactive entities to archives while ensuring durable facts are never deleted and older facts are superseded.

How does memory decay and versioning work when managing PARA folders and inactive entities?

Memory decay and versioning work by enforcing atomic fact guidelines where durable facts are never deleted but superseded by newer ones. Inactive entities within the PARA folders are automatically moved to life/archives, keeping active knowledge workspaces clean and relevant.

Why use a file-based memory system with qmd queries instead of a standard database for personal knowledge?

Use a file-based memory system with qmd queries to store knowledge as readable YAML and markdown files on disk. This approach provides durable, searchable, and version-controlled personal memory that avoids database complexity while enabling cross-session recall and weekly synthesis.