para-memory-files

Organize persistent knowledge across sessions using a PARA-based memory structure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The PARA memory system provides a structured, durable way to store and retrieve knowledge across sessions using Tiago Forte's PARA method. It organizes information into a knowledge graph (life/ areas/ projects), daily notes, and tacit knowledge to support planning, synthesis, and memory recall over time.

Core Features & Use Cases

  • Three-layer memory: knowledge graph with entities and summary.md + items.yaml; daily notes as a raw timeline; tacit knowledge about user patterns.
  • Non-destructive memory lifecycle: add facts, plan synthesis, recall, and aging rules to maintain context without losing information.
  • Cross-session planning and recall: enables weekly synthesis, memory decay handling, and rehydration of past context for informed decision making.

Quick Start

Create a new entity folder under life/ (e.g., life/people/alice) with a summary.md and items.yaml, then begin saving atomic facts to items.yaml.

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 persistent knowledge across sessions using the PARA method?▼

You can structure persistent knowledge using a PARA-based memory system that organizes information into a knowledge graph, daily notes, and tacit patterns to support planning, synthesis, and recall across sessions.

How does structured memory decay work for managing knowledge graphs?▼

Structured memory decay uses aging rules to manage knowledge graph context, enforcing non-deletion to preserve atomic facts in items.yaml while maintaining durable context for future recall.

What is the best way to store atomic facts for daily notes and projects?▼

The best way to store atomic facts is to save them as structured entries in items.yaml files within entity folders, enforcing YAML frontmatter and non-deletion rules to maintain durable project context.

Can I plan weekly synthesis and rehydrate past context using PARA folders?▼

Yes, the PARA memory structure supports cross-session planning and weekly synthesis by rehydrating past context from daily notes and the knowledge graph to inform decision making without losing information.

Do I need YAML frontmatter to maintain a non-destructive memory lifecycle?▼

Yes, YAML frontmatter is enforced to maintain a non-destructive memory lifecycle, ensuring atomic facts are preserved in items.yaml while applying structured aging rules to maintain durable context.

Why does this knowledge graph approach enforce non-deletion rules for items?▼

Non-deletion rules are enforced to preserve atomic facts and tacit knowledge in items.yaml, ensuring past context remains available for memory recall and weekly synthesis without losing information over time.