para-memory-files

Organize and persist user memory across sessions using a PARA-based file system.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Persistent, organized memory for an individual agent, enabling cross-session continuity, knowledge capture, and planning across projects.

Core Features & Use Cases

  • Three-layer memory architecture: a Knowledge Graph under life/ with summary.md and items.yaml; Daily Notes for raw timeline; Tacit Knowledge for user patterns.
  • Rules for memory lifecycle: never delete facts, supersede when updated, move inactive items to archives, weekly synthesis, and recall via qmd.
  • Use Case: maintain long-running projects, capture conversations, plan weekly syntheses, and recall past context across sessions.

Quick Start

Create the PARA memory folder structure under $AGENT_HOME and begin recording daily notes and entity memory.

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 across sessions using a PARA-based file system?

You can persist agent memory across sessions by organizing data into a PARA-based file structure under $AGENT_HOME, using YAML and Markdown schemas for facts and notes, and applying recall workflows to maintain continuity.

What is the best way to organize daily notes and knowledge capture for long-running projects?

Organizing daily notes and knowledge capture is best handled through a three-layer architecture: a Knowledge Graph with summary.md and items.yaml, raw Daily Notes for timelines, and Tacit Knowledge for user patterns.

How does the PARA method handle memory lifecycle and recall for weekly synthesis?

The PARA method handles memory lifecycle by never deleting facts, superseding updated items, moving inactive entries to archives, and using qmd-powered recall workflows to support weekly synthesis and context rehydration.

Do I need a specific directory structure to use file-based memory management?

Yes, file-based memory management requires a defined directory structure relative to $AGENT_HOME to properly store the PARA folders, daily notes, and knowledge graph layers for accurate recall.

Can I use YAML and Markdown schemas to store entity memory and project planning notes?

Yes, you can use YAML and Markdown schemas to store entity memory and project planning notes, which enables structured knowledge capture and reliable recall across different agent sessions.