skills.rest
blauwtje
blauwtjeCOMMUNITY
Explore all skills by this author →
GitHub

memory

Records user corrections about a repository into a two-session-attested project memory file.

1|Updated Sep 10, 2026
Search Tags:#claude code#hooks#memory#corrections#attestation#session persistence#repository knowledge
One-click install
npx skills add https://github.com/blauwtje/exo --skill memory-blauwtje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/blauwtje/exo/tree/main/skills/memory
Command: npx skills add https://github.com/blauwtje/exo --skill memory-blauwtje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Corrections a user gives about a repository are lost when a session ends, so the next session repeats the same mistake. This Skill keeps only corrections attested in two separate sessions and still supported by the repository, preventing a memory file that grows with stale or misheard claims. ## Core Features & Use Cases - Two-session attestation gate: Corrections are booked with a verbatim quote and session id, and written to memory only after a second session attests them and the user approves. - Budgeted, verified memory file: memory.md is rendered from memory.json under a byte budget, and verify drops lines whose referenced files or symbols no longer exist. - Correction nudge hook: A UserPromptSubmit hook detects correction markers in prompts and suggests the book command, with a stats command reporting the hit rate. - Use Case: A user corrects a wrong assumption about the build layout twice across sessions; the Skill proposes the claim with both dated quotes, and on approval writes it with file references so future sessions read it. ## Quick Start Ask the assistant to remember a correction about this repository by running the memory skill with the correction this session must not lose.

Frequently Asked Questions about memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI coding assistant remember a correction across sessions?▼

Book the correction with the memory script using --claim, --quote and --session flags. Once a second session attests the same claim and you approve the proposal, it is written to memory.md with file references.

Why does the memory skill refuse to write a correction immediately?▼

A claim must be attested in two separate sessions before it can be written, because a single session may have misheard the correction. The script reports how many attestations the booking currently has.

How does project memory stay accurate when the repository changes?▼

The verify command checks every live line's referenced paths and symbols against the repository and drops lines whose references no longer exist. Dropped lines stay in memory.json as dated history.

What happens when the memory file exceeds its byte budget?▼

The write is refused with a message naming the oldest live lines to retire first. You retire one with the retire command or archive decision history, then retry the write.

When should a correction not go into project memory?▼

Build, test or run commands belong in AGENTS.md or CLAUDE.md, and plans belong to the planning skill. Facts the repository already records, like code structure or git history, are re-read rather than remembered.

Related Skills

Explore More Software Engineering Skills→
EyhenijEyhenij
1

turn-entry

Defines how session handovers and turn maps load into context at session startup.

Community
Intermediate
cookyscookys
10

learn

Record reusable lessons and fixes into MEMORY.md for future sessions.

Community
Intermediate
mistakeknotmistakeknot
3

intermem

Synthesize stable auto-memory facts into AGENTS.md and CLAUDE.md documentation files.

Community
Intermediate
wimpysworldwimpysworld
716

how-to-contribute

Analyzes project documentation to detect contribution gates, AI bans, and prompt-injection traps.

Official
Intermediate