AgentStack
SKILL verified MIT Self-run

Para Memory Files

skill-incomestreamsurfer-paperclip-surfers-para-memory-files · by IncomeStreamSurfer

>

No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-incomestreamsurfer-paperclip-surfers-para-memory-files

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Para Memory Files? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

PARA Memory Files

Persistent, file-based memory organized by Tiago Forte's PARA method. Three layers: a knowledge graph, daily notes, and tacit knowledge. All paths are relative to $AGENT_HOME.

Three Memory Layers

Layer 1: Knowledge Graph ($AGENT_HOME/life/ -- PARA)

Entity-based storage. Each entity gets a folder with two tiers:

  1. summary.md -- quick context, load first.
  2. items.yaml -- atomic facts, load on demand.
$AGENT_HOME/life/
  projects/          # Active work with clear goals/deadlines
    /
      summary.md
      items.yaml
  areas/             # Ongoing responsibilities, no end date
    people//
    companies//
  resources/         # Reference material, topics of interest
    /
  archives/          # Inactive items from the other three
  index.md

PARA rules:

  • Projects -- active work with a goal or deadline. Move to archives when complete.
  • Areas -- ongoing (people, companies, responsibilities). No end date.
  • Resources -- reference material, topics of interest.
  • Archives -- inactive items from any category.

Fact rules:

  • Save durable facts immediately to items.yaml.
  • Weekly: rewrite summary.md from active facts.
  • Never delete facts. Supersede instead (status: superseded, add superseded_by).
  • When an entity goes inactive, move its folder to $AGENT_HOME/life/archives/.

When to create an entity:

  • Mentioned 3+ times, OR
  • Direct relationship to the user (family, coworker, partner, client), OR
  • Significant project or company in the user's life.
  • Otherwise, note it in daily notes.

For the atomic fact YAML schema and memory decay rules, see [references/schemas.md](references/schemas.md).

Layer 2: Daily Notes ($AGENT_HOME/memory/YYYY-MM-DD.md)

Raw timeline of events -- the "when" layer.

  • Write continuously during conversations.
  • Extract durable facts to Layer 1 during heartbeats.

Layer 3: Tacit Knowledge ($AGENT_HOME/MEMORY.md)

How the user operates -- patterns, preferences, lessons learned.

  • Not facts about the world; facts about the user.
  • Update whenever you learn new operating patterns.

Write It Down -- No Mental Notes

Memory does not survive session restarts. Files do.

  • Want to remember something -> WRITE IT TO A FILE.
  • "Remember this" -> update $AGENT_HOME/memory/YYYY-MM-DD.md or the relevant entity file.
  • Learn a lesson -> update AGENTS.md, TOOLS.md, or the relevant skill file.
  • Make a mistake -> document it so future-you does not repeat it.
  • On-disk text files are always better than holding it in temporary context.

Memory Recall -- Use qmd

Use qmd rather than grepping files:

qmd query "what happened at Christmas"   # Semantic search with reranking
qmd search "specific phrase"              # BM25 keyword search
qmd vsearch "conceptual question"         # Pure vector similarity

Index your personal folder: qmd index $AGENT_HOME

Vectors + BM25 + reranking finds things even when the wording differs.

Planning

Keep plans in timestamped files in plans/ at the project root (outside personal memory so other agents can access them). Use qmd to search plans. Plans go stale -- if a newer plan exists, do not confuse yourself with an older version. If you notice staleness, update the file to note what it is supersededBy.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.