agentleFS
akunzaiakunzai/agent-skills/skills/agents-memory/SKILL.md

agents-memory

Skill5 starsChanged 54 days agoMITView on GitHub

Record, recall, or forget notes in the agent's global or project memory, deciding scope (global vs. project) and tier (short-term candidate vs. long-term durable) when recording. Use on `/agents-memory`, `$agents-memory`, "remember this", "what did I note about X", "recall", or "forget X". Autonomous knowledge capture after solving a problem is agents-md's Prevent Recurrence, not this skill.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write directly into the durable target — no intermediate staging or batch review:

    line 33
  2. Distinctive:

    Before writing, hold the note to this bar:

    line 40
  3. Distinctive:

    Always show the exact addition and get explicit confirmation before writing to a durable file.

    line 50
  4. Very specific:

    If absent, read migration and ask to copy all projects, mapping each <name>-<hash6> to its own <name>.

    line 70
  5. Distinctive:

    Keep verified backups and conflicting notes.

    line 72
  6. Distinctive:

    No retention policy or note resolution markers.

    line 74

≈ “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

agents-memory — Explicit Memory

Records one thing the user explicitly asked to remember, and recalls or forgets short-term notes on request.

Scope and tier

Two independent decisions, each resolved from an explicit argument, semantic inference from the request, or by asking when genuinely ambiguous:

  • Scope — global (~/.agents/..., read by every agent and project) or project (this repo only).
  • Tier — long-term (durable, timeless, must be explicitly requested) or short-term (dated candidate; the default when ambiguous).

When tier is long-term

Write directly into the durable target — no intermediate staging or batch review:

  • Global: ~/.agents/AGENTS.md
  • Project: <repo>/AGENTS.md, where <repo> is the git root of the current working directory (the directory itself outside git) — never the directory this skill was loaded from.

Before writing, hold the note to this bar:

  • Verified — proven to work in this workspace, not a guess.
  • Reusable — likely useful again, not one-off task progress.
  • Stable — a lasting convention, not a temporary hack.
  • Strip time-of-day stamps (e.g. [HH:MM]) — durable files are timeless.

Placement — a root line or a topic doc behind a pointer — and the size budget follow the agents-md skill.

Always show the exact addition and get explicit confirmation before writing to a durable file.

When tier is short-term

Land the note as its own file — one file per note, not appended to a shared log:

~/.agents/memories/YYYY-MM-DD-<slug>.md                          # global
~/.agents/memories/projects/<project-name>/YYYY-MM-DD-<slug>.md   # project
  • YYYY-MM-DD is today's date.
  • <slug> is a short, agent-chosen topic slug, so the filename alone identifies the content without opening the file.
  • Resolve <project-name> with scripts/proj-memory-path.sh; --ensure also creates the directory.
  • <project-name> preserves the root name exactly: main repo for worktrees, target outside Git. Same-name projects share memory; rename to isolate.
  • For project memory, check ~/.agents/memories/.project-name-migration-v1. If absent, read migration and ask to copy all projects, mapping each <name>-<hash6> to its own <name>. Keep verified backups and conflicting notes; remove old directories only after verification. Mark completion after cleanup. Otherwise skip legacy scans.
  • No retention policy or note resolution markers. Delete obsolete notes only after explicit confirmation.
  • Recall: search these directories directly with grep/ls.

Never write

Passwords, tokens, credentials, PII, or unverified speculation — see references/security.md for the full list and how to redact instead of dropping a note entirely.

Cross-agent global memory setup

Wiring a newly installed coding agent's own native global memory file to ~/.agents/AGENTS.md is a one-time setup task, not a memory-capture action — see references/cross-agent-locations.md for the per-agent path table. There is no dedicated script for this; wire the file by hand, in whatever way fits its format, and back up any existing real file first.

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.