paperclipai/para-memory-files
skills/para-memory-files/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add paperclipai/paperclip para-memory-filesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 10, 2026, 9:19 AM196.6s2 files scanned
SKILL.md
- name:
- para-memory-files
- description:
- >
- three memory layers:
- (1) Knowledge graph in PARA folders with atomic YAML facts,
- Trigger on any memory operation:
- saving facts, writing daily notes, creating
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:
summary.md-- quick context, load first.items.yaml-- atomic facts, load on demand.
$AGENT_HOME/life/
projects/ # Active work with clear goals/deadlines
<name>/
summary.md
items.yaml
areas/ # Ongoing responsibilities, no end date
people/<name>/
companies/<name>/
resources/ # Reference material, topics of interest
<topic>/
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.mdfrom active facts. - Never delete facts. Supersede instead (
status: superseded, addsuperseded_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.
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.mdor 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.
Related Skills
paperclipai/paperclip
tools
VerifiedTrustedCommunity
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
63,111SKILL.mdUpdated Apr 10, 2026
paperclipai/terminal-bench-loop
tools
VerifiedTrustedCommunity
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an issue asks to "run Terminal-Bench in a loop", "drive Terminal-Bench until it passes", "loop fix-git through Paperclip", or otherwise points at a Terminal-Bench task and asks for bounded iteration with diagnosis.
62,078SKILL.mdUpdated May 4, 2026
paperclipai/paperclip-create-agent
tools
VerifiedTrustedCommunity
Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
62,078SKILL.mdUpdated Apr 10, 2026
paperclipai/diagnose-why-work-stopped
development
VerifiedTrustedCommunity
How to handle "why did this work stop / why is this looping?" assignments. Forensics first on the named tree, surface the exact stop-point, frame the fix as a general product rule that respects three invariants (productive work continues, only real blockers stop work, no infinite loops), and deliver a plan — no code changes — gated by board/CTO approval before child issues are created. Use whenever the issue title or body asks for forensics on a stalled, looping, or "went too deep" tree.
61,120SKILL.mdUpdated May 1, 2026