AugmentClaude

Remnic Remember

Store shared memories that all connected agents can access later.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/remnic-remember-joshuaswarren/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Store a durable memory in Remnic so every connected agent can recall it. Trigger phrases include "remember this", "save this for later", "add a note that".

What this skill does

When to use

Use when the user explicitly asks Claude Code to remember something, or when a turn produces a durable decision, preference, or finding worth storing for later sessions.

Triggers:

  • "Remember that …"
  • "Save this for later."
  • /remnic:remember <text> slash command invocation.
  • End-of-turn consolidation after a non-trivial conclusion.

Inputs

  • content (required) — the statement to store, in the user's own words where possible.
  • Optional: category hint (preference, decision, fact, procedure).
  • Optional: related entity or project name.

Procedure

  1. Confirm the content is durable — it should still be useful days or weeks from now.
  2. Strip any secrets, credentials, or transient context.
  3. Keep the user's voice; rephrase only when needed for clarity.
  4. Call remnic_memory_store with the text as content. Include category or entity hints when the tool accepts them.
  5. Confirm to the user in one line what was stored.
  6. Mention that the memory is available across connected agents (Claude Code, Codex, Hermes, OpenClaw).

Efficiency plan

  • Batch related facts into a single memory rather than writing many tiny ones.
  • If a prior memory on the same topic exists, update it rather than duplicating.
  • Do not store anything easily re-derived from source code or docs.

Pitfalls and fixes

  • Pitfall: Storing transient state. Fix: Only commit facts that will still matter tomorrow.
  • Pitfall: Leaking secrets. Fix: Redact before calling the tool.
  • Pitfall: Duplicates on the same topic. Fix: Recall first; prefer update.
  • Pitfall: Vague entries. Fix: Be specific — who, what, when, why.

Verification checklist

  • Content is durable and specific.
  • No secrets or PII were included.
  • remnic_memory_store was called with the final content.
  • User received a one-line confirmation.
  • Canonical remnic_memory_store was used over legacy engram_memory_store.

Tool names: canonical name is remnic_memory_store. The legacy engram_memory_store alias remains accepted during v1.x.

Related skills