agentleFS
Sign inStart free
sherificansherifican/Agent-FleetOps/skills/agent-memory-ops/SKILL.md

agent-memory-ops

Skill34 starsChanged 37 days agoMITView on GitHub

Maintain durable agent rules separately from episodic context and keep a compact memory index.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Put a durable rule only in the durable tier.

    line 13
  2. Distinctive:

    Before creating a memory, search for an existing entry and update it when it covers the same subject.

    line 14
  3. Distinctive:

    Keep one durable fact per entry, with a stable identifier, a short retrieval-oriented description, type metadata, and application guidance …

    line 15
  4. Distinctive:

    Keep the memory index as pointers only.

    line 16
  5. Distinctive:

    Do not store facts already reliably represented by source control or the repository unless a cross-session decision needs explanation.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Memory Operations

Memory tiers

  • Durable tier: standing rules, decisions, preferences, and non-obvious facts that must survive sessions. This is the authoritative tier.
  • Episodic tier: temporary observations, session signals, and supporting evidence. It is not the place for binding rules.

Rules

  1. Put a durable rule only in the durable tier; never rely on an episodic note to carry a binding instruction.
  2. Before creating a memory, search for an existing entry and update it when it covers the same subject.
  3. Keep one durable fact per entry, with a stable identifier, a short retrieval-oriented description, type metadata, and application guidance where useful.
  4. Keep the memory index as pointers only. Put substantive content in the individual entry.
  5. Do not store facts already reliably represented by source control or the repository unless a cross-session decision needs explanation.

Pitfalls

  • Duplicating a rule with slightly different wording.
  • Putting full memory content in an index file.
  • Saving transient conversation detail that will create noisy retrieval.

Verification checklist

  • The information was classified as durable or episodic.
  • Existing coverage was checked.
  • Durable entries have required metadata and a concise index pointer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free