Stats
Actions
Tags
From engram
Use when storing or updating durable project memory via the engram MCP tools — enforces durable-only capture, search-before-store, supersede-on-contradiction, and the two-tier spine/overlay scope. Trigger when the user states a durable decision/preference/convention, on the session-end capture nudge, and before any mcp__engram__store_memory / update_memory / delete_memory call.
How this skill is triggered — by the user, by Claude, or both
Slash command
/engram:curating-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The memory store is **explicit and zero-junk**: only deliberately chosen durable
The memory store is explicit and zero-junk: only deliberately chosen durable facts live in it, and it stays correct over time. Apply this discipline before every memory write.
STORE (durable): decisions, preferences, conventions, gotchas, and project-specific facts that outlive the session.
DO NOT STORE: transient state, current activity/progress, secrets or API keys, timestamps, one-off tool output, or anything trivially re-derivable.
mcp__engram__search_memory across both
the spine and (if present) the workspace overlay first. search_memory is
backed by a semantic/vector engine, so query it with a natural-language
description of the fact (not keyword fragments) — it surfaces conceptually
related records even when they share no exact wording. If a near-duplicate
exists, update it instead of adding a new record.update_memory (preferred) or delete_memory the stale
record. Do not treat a spine fact and a divergent workspace-overlay fact
as a contradiction — they are parallel truths by design.Memory spine scope from
session start) — most durable facts are repo-wide and should follow the user
into every workspace. Store to the overlay (Memory workspace scope)
only when a fact is genuinely local to this line of work and would be wrong
or premature elsewhere (e.g. an in-flight decision that contradicts main
until merged). Promotion of overlay facts to the spine when work merges is
the promoting-memory skill.source honestly (user-said vs agent-inferred). Do
not set actor — it is assigned server-side from the validated OAuth token.All tools are on the engram server: mcp__engram__store_memory,
…__search_memory, …__update_memory, …__delete_memory, …__list_memory,
…__get_memory. If a call returns 401/403 the server is not authenticated —
tell the user to authenticate via /mcp (engram → Authenticate), and
restate the durable fact so they can re-store it after authenticating; never
drop it silently.
npx claudepluginhub seanb4t/engram --plugin engramProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.