From agd-memory
Saves facts, decisions, project details, or preferences to agd-memory via /remember or phrases like 'remember this', 'save to memory'. Direct save or interactive draft+confirm modes.
npx claudepluginhub pinperepette/agd-memory --plugin agd-memoryThis skill uses the workspace's default tool permissions.
Explicit channel to add a fact to the per-project memory. The recall
Saves key project knowledge explicitly to MEMORY.md via /si:remember for reliable recall. Checks duplicates, warns on size, suggests CLAUDE.md promotion.
Saves decisions, preferences, patterns, lessons, and project context to Claude Code's persistent memory directory as structured markdown files, with duplicate checks and index updates for cross-session recall.
Captures durable knowledge from Claude Code sessions into rekal memory with deduplication via search/store/supersede. Triggers at session end, task finish, or key preferences/decisions.
Share bugs, ideas, or general feedback.
Explicit channel to add a fact to the per-project memory. The recall
skill is memory; this is its write counterpart.
With an argument — /remember <text> or "ricorda che X":
the user provided the content. Derive kind, id, desc from the
text (rules below), call agd_memory_save, confirm with one short
line.
Without an argument — /remember alone, or "salvalo":
take the last few user/assistant turns as input, draft a single block
{kind, id, desc, content}, present it to the user as a preview, wait
for explicit ok before saving. If the user revises (different scope,
shorter content, etc.), update the draft and ask again.
Never save without an explicit confirmation in mode-without-argument.
kindThe MCP agd_memory_save schema restricts kind to four values:
| value | use for |
|---|---|
x-user | identity, preferences, working style of the user |
x-feedback | corrections, rules-of-collaboration, decisions, learnings of the session |
x-project | what this project is, scope, current focus |
x-reference | reusable technical knowledge: paths, versions, commands, gotchas, schemas |
If ambiguous → default to x-feedback. Never invent a custom x-…
kind via this skill: the MCP enum will reject it client-side.
idStable, kebab-case, semantic. Heuristic:
agd-mcp-kind-enum).-, strip non [a-z0-9-].agd_memory_toc) for collisions:
replace (update existing entry).-2, -2026-05-10, or
a more specific qualifier.Never overwrite silently. If you would replace an entry whose meaning differs from the new content, surface this to the user first.
descOne short line, ≤60 chars, present-tense, describes WHY this is in memory. Examples:
desc is what the TOC shows; make it good enough to decide without
fetching the body.
Save only what would be lost if the session ended and would matter in a future session:
Do not save:
git logWhen in doubt: ask the user one short clarifying question before saving.
Confirm with a single line: saved #<id> (<kind>) — <desc>.
Don't restate the body.
If the body contains a standalone ~~~ line, the save will be
rejected by the plugin (≥ v0.1.1 enforces this — the body would
otherwise corrupt the file). Reword and retry; explain why.