From plur
Extracts durable learnings (corrections, conventions, preferences) at session end and saves them as structured engrams for future reuse.
How this skill is triggered — by the user, by Claude, or both
Slash command
/plur:plur-session-endThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run this at the end of a conversation to extract what is worth remembering.
Run this at the end of a conversation to extract what is worth remembering.
PLUR stores durable knowledge — corrections, conventions, preferences, decisions. It does not store session logs, one-off status, or anything that will be irrelevant next week. This skill enforces that discipline.
Scan the conversation for:
| Category | Examples |
|---|---|
| Corrections | "No, the API returns snake_case" / "Don't use X, use Y" |
| Preferences | "Always run lint before committing" / "User prefers concise explanations" |
| Codebase conventions | "This project uses repository pattern" / "Tests live in __tests__/" |
| Decisions | "We chose PostgreSQL for ACID compliance" |
| Gotchas | "The staging env needs NODE_ENV=staging, not production" |
| Terminology | "They call it a 'slot' not a 'channel'" |
Skip:
Format: a single clear statement that will make sense to a future agent with no session context.
Good: "The publish script requires npm 2FA — always run 'npm publish' interactively, never from CI."
Bad: "We talked about the publish issue."
For each learning, determine:
type: correction | preference | convention | decision | gotcha | factdomain: the project, library, or topic area (e.g., "plur", "typescript", "project:acme")scope: the scope of applicability (e.g., "global", "project:acme")tags: 2–5 descriptive tagsIf plur_learn is available:
plur_learn(statement, { type, domain, scope, tags })
Call once per learning. Do not batch into one call — separate engrams decay and strengthen independently.
If plur_session_end is available, pass learnings as engram_suggestions for batch review.
Fewer, stronger engrams beat many weak ones.
Session learnings saved (3 engrams):
1. [correction] The API returns timestamps in Unix seconds, not milliseconds.
domain: project:acme | tags: api, timestamps
2. [preference] User prefers TypeScript strict mode — always enable in tsconfig.
domain: typescript | tags: tsconfig, preferences
3. [gotcha] The staging deploy requires a manual cache bust at /admin/cache.
domain: project:acme | tags: deploy, staging, ops
Keep the user-facing summary short. Show what you saved; do not narrate your reasoning.
This skill pairs with plur-memory:
plur-memory runs continuously — it injects relevant engrams at the start of each turnplur-session-end runs once — it extracts and saves what the session producedTogether they close the memory loop: inject at start, learn at end.
npx claudepluginhub plur-ai/plurPersistent memory for AI agents using open engram format. Learns from corrections, remembers across sessions, and transfers knowledge across domains via automatic injection and explicit learn/forget commands.
Persists learnings into a 5-layer memory hierarchy (CLAUDE.md files, memory/MEMORY.md) and consolidates by pruning outdated entries and promoting recurring patterns. Triggers on 'extract learnings', 'remember', 'dream'.
Analyzes coding sessions for key decisions, outcomes, and patterns worth remembering, then stores user-confirmed items via Pensyve. Use at session end.