Save one durable work fact to the project's configured memory surface.
npx skills add https://github.com/reddb-io/red-skills --skill store-reddb-io
Please help me install this Agent Skill. Skill: store Source: https://github.com/reddb-io/red-skills/tree/main/plugins/memory/skills/core/store Command: npx skills add https://github.com/reddb-io/red-skills --skill store-reddb-io
.red/memory/notes/; in graph mode it writes a deduped node to the RedDB store in .red/memory/graph.rdb. - Deduplication: Storing the same fact twice in graph mode returns the same node identity instead of creating duplicates. - Boundary enforcement: Routes personal facts to brain capture and refuses secrets, keeping memory notes safe to commit. - Use Case: After deciding to pin a dependency version because of a breaking upstream change, run /memory:store with the reasoning so future sessions recall the why behind the pin. ## Quick Start Ask the agent to remember a decision or gotcha, for example: remember that we pin lodash to 4.17.21 because version 5 breaks the build.High-intent search queries and answers about installing and using this skill.
Run the store command with the fact text, for example /memory:store followed by the decision. The CLI writes a markdown note or graph node depending on your memory configuration and reports the stored identity.
Markdown-only mode writes a timestamped note with YAML frontmatter under .red/memory/notes/ as the canonical, committable store. Graph mode writes a deduped node to the RedDB store in .red/memory/graph.rdb with metadata for governed recall and supersession.
The store command requires memory init to have run first. If memory is not configured for the project, run /memory:init to set up the storage surface before storing any facts.
No. Personal facts like biographical details and long-lived human preferences should go to brain capture instead. Secrets must never be stored because notes are plain text on disk and may be committed to version control.
In graph mode, storing the same fact twice returns the same node identity because writes are deduplicated. This keeps the memory store clean and avoids redundant entries for repeated facts.
dmae97Classify coding agent memories and generate evidence bundles for audit replay.
DaveSteadmanStore and recall user facts, preferences, and project context in a structured JSON file.
TasiTechCapture durable user facts and preferences into a local memory store.
nebinfraOrganize user knowledge across sessions using PARA file structures.