Help us improve
Share bugs, ideas, or general feedback.
From Memsy
Saves facts, decisions, and context to Memsy memory for future sessions. Strips framing verbs and persists the substance verbatim via memsy_ingest.
npx claudepluginhub memsy-io/memsy --plugin memsyHow this skill is triggered — by the user, by Claude, or both
Slash command
/memsy:memsy-rememberThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user wants to commit something to Memsy memory. Run this workflow:
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.
Save information to Memex long-term memory. Captures the given text (or infers the most important context from the conversation) as a persistent note.
Share bugs, ideas, or general feedback.
The user wants to commit something to Memsy memory. Run this workflow:
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. This rule must match the smart-router skill and the /memsy:memsy-remember command exactly — three converging paths must store the same content for the same input.
| 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 rather than guessing. Drop only the framing verb; preserve every substantive word.
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."If your session context contains the line [memsy modes: ... confirm-before-store ...] (emitted by the SessionStart hook when MEMSY_CONFIRM_STORE=on), the user has opted into explicit-permission mode. 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.
A single event:
kind: "user_message"content: the substantive text from step 1 (verbatim, no padding)ts: current ISO 8601 timestampDo NOT add role_id / team_id unless the user explicitly specified them — let the user's defaults from memsy_set_defaults apply.
✓ Stored in Memsy.
Content: <first 80 chars>...
Event: <event_id, first 8 chars>
Use /memsy <query> to find it later.
Hand off to the memsy-setup skill. Be explicit that the memory was NOT saved. Do not silently swallow the failure or pretend it worked.