New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Remnic Memory Workflow

by joshuaswarren in joshuaswarren/remnic

Shared memory workflow for Remnic-connected agents — recall before acting, observe during work, remember at the end.

MITAuto-check passed

Install Remnic Memory Workflow

skills CLI
$ npx skills add joshuaswarren/remnic --skill remnic-memory-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install joshuaswarren/remnic remnic-memory-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/joshuaswarren/remnic.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/remnic-core/skills/remnic-memory-workflow .claude/skills/remnic-memory-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
remnic-memory-workflow
GitHub stars
218
Token cost
~954 tokens
SKILL.md length
463 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Shared memory workflow for Remnic-connected agents — recall before acting, observe during work, remember at the end.

  • Works in 6 steps: Recall first. Call remnic_recall with a… → Mention relevant memories briefly to the… → Observe during work. For significant… → …
  • Phrases include what do you remember about
  • SKILL.md covers When to use, Inputs, Procedure and Efficiency plan, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Remnic Memory Workflow is an agent skill from joshuaswarren/remnic. Shared memory workflow for Remnic-connected agents — recall before acting, observe during work, remember at the end. Trigger phrases include "what do you remember about", "save this for later", "any context from last time".

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Model Context Protocol. The repository describes itself as: Open-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access. The licence is MIT.

When your agent uses it

  • Phrases include what do you remember about
  • Save this for later
  • Any context from last time

Example prompts

  • “what do you remember about”
  • “save this for later”
  • “any context from last time”
  • “/remnic-memory-workflow”

Requirements

  • Pre-approved tools (allowed-tools): remnic_recall, remnic_memory_store, remnic_lcm_search, remnic_entity_get, remnic_observe

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Recall first. Call remnic_recall with a concise natural-language query derived from the user's request. Pull 3–8 results. Skim them for…
  2. Mention relevant memories briefly to the user if they materially change the plan, otherwise quietly use them as context.
  3. Observe during work. For significant tool outputs (file edits, command exits, test results) call remnic_observe so Remnic can keep its…
  4. Deep search when needed. If remnic_recall misses something the user insists exists, call remnic_lcm_search with a more literal phrase.
  5. Browse entities. When the user references a specific project, person, or concept by name, call remnic_entity_get to pull its facts and…
  6. Remember at the end. Before ending the turn, store any durable decision, preference, or finding with remnic_memory_store. Keep each entry…

What it can do on your machine

Read from SKILL.md and the folder at commit 002ea68. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • remnic_recall
    • remnic_memory_store
    • remnic_lcm_search
    • remnic_entity_get
    • remnic_observe

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Remnic Memory Workflow loads about 954 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 463 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~954

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from joshuaswarren/remnic at commit 002ea68, republished under its MIT licence (© joshuaswarren). 463 words, ~954 tokens.

Download SKILL.mdSave it as .claude/skills/remnic-memory-workflow/SKILL.md (or your agent's skills folder).
name
remnic-memory-workflow
description
Shared memory workflow for Remnic-connected agents — recall before acting, observe during work, remember at the end. Trigger phrases include "what do you remember about", "save this for later", "any context from last time".
allowed-tools
remnic_recall, remnic_memory_store, remnic_lcm_search, remnic_entity_get, remnic_observe
disable-model-invocation
false

When to use

Use this skill as the default playbook whenever an agent picks up a task that could benefit from prior context, or when the user explicitly asks the agent to remember or recall something. It is the umbrella workflow — individual skills (remnic-recall, remnic-remember, remnic-search, remnic-entities, remnic-status) implement the detailed steps.

Triggers:

  • The user opens a new task, ticket, or branch.
  • The user says "what do you know about X", "have we talked about Y before", "remind me of Z".
  • The user asks the agent to save a preference, decision, or fact.
  • A long-running turn produces a durable outcome worth capturing.

Inputs

  • Current user request (natural language).
  • Optional: active project path, ticket number, branch name.
  • Optional: topic keywords surfaced earlier in the session.

Procedure

  1. Recall first. Call remnic_recall with a concise natural-language query derived from the user's request. Pull 3–8 results. Skim them for anything relevant.
  2. Mention relevant memories briefly to the user if they materially change the plan, otherwise quietly use them as context.
  3. Observe during work. For significant tool outputs (file edits, command exits, test results) call remnic_observe so Remnic can keep its ambient context fresh.
  4. Deep search when needed. If remnic_recall misses something the user insists exists, call remnic_lcm_search with a more literal phrase.
  5. Browse entities. When the user references a specific project, person, or concept by name, call remnic_entity_get to pull its facts and relationships.
  6. Remember at the end. Before ending the turn, store any durable decision, preference, or finding with remnic_memory_store. Keep each entry under ~300 tokens.
Show full SKILL.md (204 more words)Show less

Efficiency plan

  • Batch recalls. One broad query is usually cheaper than several narrow ones.
  • Skip recall for trivially local requests (e.g., "format this JSON").
  • Reuse the current turn's recall results instead of re-querying within the same turn.
  • Store each memory once. If you are about to store something you just recalled, update instead of duplicating.

Pitfalls and fixes

  • Pitfall: Storing transient task state ("user is running tests now"). Fix: Only store facts with durable value — decisions, preferences, conclusions, long-lived context.
  • Pitfall: Leaking secrets into memories. Fix: Redact API keys, tokens, and credentials before calling remnic_memory_store.
  • Pitfall: Drowning the user in recalled context. Fix: Summarize in 1–3 bullet points; offer to expand on request.
  • Pitfall: Forgetting the write. Fix: Make "remember the decision" the last step of any non-trivial turn.

Verification checklist

  • Recall was attempted before the agent committed to a plan.
  • Any user-facing mention of recalled context was concise and attributed.
  • Durable decisions, preferences, and findings were stored via remnic_memory_store.
  • No secrets, credentials, or transient state were written.
  • Legacy engram_* aliases were NOT preferred over canonical remnic_* tool names.

Tool names: this skill uses the canonical remnic_* MCP tools. Legacy engram_* aliases (engram_recall, engram_memory_store, engram_lcm_search, engram_entity_get, engram_observe) remain accepted during v1.x for backward compatibility.

© joshuaswarren, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/remnic-core/skills/remnic-memory-workflow of joshuaswarren/remnic.

Open the folder on GitHubat commit 002ea68

Compare with similar skills

Remnic Memory Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Remnic Memory Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Remnic Memory Workflow this skilljoshuaswarren/remnic218—~954Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills8.5k6 repos~3.2kAutomated safety check: NotesApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Figma use_figma Plugin API Rules

    warpdotdev/warp

    Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed

  • Stitch to Remotion Walkthrough Videos

    google-labs-code/stitch-skills

    Official

    Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.

    8.5k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check: notes

  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

More from joshuaswarren/remnic

  • Remnic Entities

    joshuaswarren/remnic

    Browse entities in the Remnic knowledge graph and surface their facts and relationships.

    218 GitHub stars~612 tokensUpdated today
    Auto-check passed

  • Remnic Memory Workflow

    joshuaswarren/remnic

    Shared memory workflow for Claude Code agents connected to Remnic — recall before acting, observe during work, remember at the end.

    218 GitHub stars~806 tokensUpdated today
    Auto-check passed

  • Remnic Recall

    joshuaswarren/remnic

    Search Remnic memories by natural-language query. An agent skill from joshuaswarren/remnic.

    218 GitHub stars~556 tokensUpdated today
    Auto-check passed

  • Remnic Remember

    joshuaswarren/remnic

    Store a durable memory in Remnic so every connected agent can recall it.

    218 GitHub stars~651 tokensUpdated today
    Auto-check passed

  • Remnic Search

    joshuaswarren/remnic

    Run a deep full-text search across every Remnic memory. An agent skill from joshuaswarren/remnic.

    218 GitHub stars~562 tokensUpdated today
    Auto-check passed

  • Remnic Status

    joshuaswarren/remnic

    Check the health of the Remnic daemon, stores, and connected clients.

    218 GitHub stars~557 tokensUpdated today
    Auto-check passed

Works with

Questions about Remnic Memory Workflow

What does Remnic Memory Workflow do?

Shared memory workflow for Remnic-connected agents — recall before acting, observe during work, remember at the end. Remnic Memory Workflow is an agent skill from joshuaswarren/remnic. Shared memory workflow for Remnic-connected agents — recall before acting, observe during work, remember at the end.

When should I use Remnic Memory Workflow?

Remnic Memory Workflow fits situations like: phrases include what do you remember about; save this for later; any context from last time.

How do I install Remnic Memory Workflow in Claude Code?

Run `npx skills add joshuaswarren/remnic --skill remnic-memory-workflow -a claude-code`. Or copy the skill folder (packages/remnic-core/skills/remnic-memory-workflow in joshuaswarren/remnic) into .claude/skills/remnic-memory-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Remnic Memory Workflow in Codex?

Run `npx skills add joshuaswarren/remnic --skill remnic-memory-workflow -a codex`. Or copy the skill folder (packages/remnic-core/skills/remnic-memory-workflow in joshuaswarren/remnic) into .agents/skills/remnic-memory-workflow in your project. Codex loads it when a task matches its description.

Can I use Remnic Memory Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add joshuaswarren/remnic --skill remnic-memory-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/remnic-memory-workflow, .gemini/skills/remnic-memory-workflow, .github/skills/remnic-memory-workflow and .opencode/skills/remnic-memory-workflow in your project.

What does Remnic Memory Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Remnic Memory Workflow is instructions for the agent only. Its frontmatter pre-approves these tools: remnic_recall, remnic_memory_store, remnic_lcm_search, remnic_entity_get, remnic_observe.

Does Remnic Memory Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Remnic Memory Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Remnic Memory Workflow use?

Remnic Memory Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Remnic Memory Workflow use?

About 954 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Remnic Memory Workflow?

Skills that share tags, products or a category with Remnic Memory Workflow: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Remnic Memory Workflow?

joshuaswarren (a GitHub user) maintains it in joshuaswarren/remnic, which has 218 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 11, 2026.

Source: joshuaswarren/remnic on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.