Agent skill
Memory curation
Decide what is worth remembering and keep lasting context separate from everyday noise.
Use this skill
Install it into a project with the Skills CLI, or read the files below and adapt them to your own agent.
npx skills add shan8851/agent-skills --skill memory-curationSKILL.md
View this file on GitHub---
name: memory-curation
description: Curate and promote memory with signal-first judgment. Use when running memory checkpoints, consolidating daily notes, deciding what to store in durable memory, or when the user says “remember this”. Apply a strict rubric so only stable decisions/preferences/policies are promoted to long-term memory.
---
# Memory Curation
Signal-first memory workflow.
## Core rule
Do not treat all context as memory. Prefer quality over volume.
## Workflow
1) Collect candidate facts from recent conversation/work.
2) Score each candidate using `references/promotion-rubric.md`.
3) Route each candidate:
- Durable + behavior-changing → `MEMORY.md`
- Session/day context → daily memory file
- Low-signal/noise → skip
4) Write concise bullets using `references/write-templates.md`.
5) De-duplicate against recent entries before writing.
## Hard guardrails
- Never store secrets, API keys, or sensitive credentials.
- Avoid personal/private details unless explicitly required by the user.
- Prefer one precise bullet over multiple vague bullets.
- If uncertain, keep in daily memory first; promote later if it recurs.
## Promotion defaults
Promote when at least one is true:
- explicit remember intent
- standing policy/guardrail
- stable preference (likely 30+ days)
- canonical tooling/path/routing correction
- recurring operating rule
## Completion behavior
When running silent checkpoint workflows, end with exactly `NO_REPLY`.
references/promotion-rubric.md
View this file on GitHub# Promotion Rubric
Use this rubric to decide if a candidate belongs in durable memory.
## Promote to durable memory if ANY applies
1. User explicitly says to remember it.
2. It changes assistant behavior (policy, rule, guardrail, routing).
3. It is a stable preference likely to persist for 30+ days.
4. It is a canonical location/path/tooling correction that prevents repeat mistakes.
5. It is a recurring workstream/schedule rule.
## Keep in daily memory only
- One-off updates or status pings
- Temporary plans likely to change soon
- Low-signal chatter/brainstorm fragments
## Fast scoring filter (required)
Score every candidate 0-2 each:
- Behavior impact
- Durability
- Recurrence
Guideline:
- Score >= 4 → eligible for durable memory
- Score < 4 → daily memory
references/write-templates.md
View this file on GitHub# Write Templates
## Durable memory bullet template
- **<topic> (<YYYY-MM-DD>):** <durable rule/preference/decision in one clear sentence>.
## Daily memory bullet template
- HH:MM — <specific update/decision/context delta>.
## Style
- Be concrete and behavior-oriented.
- Avoid multi-line prose when one line works.
- Include date context when useful for future interpretation.