agentleFS
AIOSAIAIOSAI/AIPass/.agents/skills/memo/SKILL.md

memo

Skill312 starsChanged 10 days agoMITView on GitHub

Update branch memory files after completing work. Saves session history, key learnings, and collaboration observations to .trinity/ files.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    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. Very specific:

    Read .trinity/passport.json first — re-absorb your identity, role, and principles before writing memories

    line 12
  2. Distinctive:

    Update each file below as needed

    line 14

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “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

Memory Update

Purpose: Update branch memory files after completing work this session.

Execution

  1. Read .trinity/passport.json first — re-absorb your identity, role, and principles before writing memories
  2. Review what was done this session (context, recent changes, key decisions)
  3. Update each file below as needed
  4. Confirm completion — list files updated

Memory Roles

Each memory file plays a distinct role. Update based on what actually changed this session.

  • .trinity/passport.json — IDENTITY. Who you are: role, capabilities, principles. Only update if identity genuinely evolved this session. Don't touch it just to touch it.
  • .trinity/local.json — YOUR MEMORY. Session history and key_learnings. Add a session entry for significant work. Add key_learnings for facts you'd need next time. Trim oldest sessions if over 20.
  • .trinity/observations.json — YOUR MEMORY OF THE USER. Collaboration insights, preferences, friction points, flow states. Skip entirely if nothing new about the user this session.

If Relevant

  • README.md — Does it reflect current state? Update if stale.

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.