| name | memsy-remember |
| description | Use this skill when the user explicitly asks to save, note, or persist a fact, decision, or piece of context for future sessions. Trigger phrases include "remember that", "save this decision", "note that", "let's remember", "store this", "tag this as", "for future reference", or any clear save-intent statement. Calls memsy_ingest MCP tool to persist the substance. |
The user wants to commit something to Memsy memory. Run this workflow:
1. Extract the substance
Strip the leading verb / framing (remember that, save this, note that, let's remember, tag this as, for future reference) and keep the substance verbatim.
| User said | Store |
|---|
| "Remember that we picked Postgres for billing because it's already deployed" | we picked Postgres for billing because it's already deployed |
| "Let's note that the rate limiter rewrite is scoped to v0.4, not v0.3" | the rate limiter rewrite is scoped to v0.4, not v0.3 |
| "Tag this as a decision: we're not adding GraphQL" | a decision: we're not adding GraphQL |
Do not paraphrase, rewrite, or invent context. If the result wouldn't be intelligible standalone (e.g. resolves to a pronoun with no antecedent), ask the user to expand.
2. Pre-flight checks — refuse / clarify if
- Too short (< 20 chars): ask the user to expand.
- Contains a secret-shaped token (
msy_, sk_, ghp_, Bearer , anything resembling an API key, password, or JWT): refuse. Say: "That looks like it contains a secret — Memsy stores in plain text. Either paraphrase without the secret, or use a real secret manager."
- Transient / scratch content (TODOs for the current turn, half-formed debug output): ask if they really want to persist it.
- Already-stored: if you just stored something nearly identical this session, skip and tell the user it's a duplicate rather than storing it again.
3. Confirm-before-store (if enabled)
If your session context contains the line [memsy modes: ... confirm-before-store ...] (emitted by the SessionStart hook when MEMSY_CONFIRM_STORE=on), surface the proposed content and ask before calling the tool:
Memsy will store:
<stripped substance from step 1>
Save? (y / n / edit "<new text>")
y / "save it" → proceed to step 4.n / "don't" → say "Not stored." and stop. Do not call memsy_ingest.edit "..." → use the new text as the content and proceed.
If the mode line isn't in context (default), skip this step — the auto-fire trigger already implies user intent.
4. Call memsy_ingest
A single event:
kind: match the speaker the substance came from — "user_message" when the user is asserting it (the usual case, e.g. "remember that I prefer X"); "assistant_message" when they're asking you to save something you (the assistant) produced or concluded. Don't blindly use user_message.content: the substantive text from step 1 (verbatim)ts: current ISO 8601 timestamp
Do NOT add role_id / team_id unless the user explicitly specified them — let their defaults from memsy_set_defaults apply.
5. Confirm back
✓ Stored in Memsy.
Content: <first 80 chars>...
Event: <event_id, first 8 chars>
6. If the tool errors out
Call memsy_health to diagnose. Be explicit that the memory was NOT saved. Do not silently swallow the failure.
Anti-noise rules — DO NOT fire when
- The user is asking a question ("did we decide...?" → that's recall, not store).
- The user is describing current state without save intent.
- The "save" verb refers to a file save ("save this to foo.ts") — use Write, not Memsy.
