agentleFS
SparkDevNetworkSparkDevNetwork/Rock/.claude/skills/remember/SKILL.md

remember

Skill701 starsChanged 43 days agoNo licenceView on GitHub

Audit the current session for things worth saving to auto-memory and present them as a plan-mode draft for explicit user approval before writing. Also identifies bubble-up candidates — rules that arguably belong in team-shared memory (CLAUDE.md or .claude/rules/) instead of private auto-memory — and surfaces them as suggestions without writing them. Use when the user says "remember", "/remember", "save what we learned", "capture this session", or wants a deliberate retrospective pass on a long session before context fades. Reads MEMORY.md plus every individual memory file first to dedupe; classifies each candidate as user / feedback / project / reference; drafts full bodies; awaits ExitPlanMode approval before writing anything. Do NOT use for: editing CLAUDE.md (that is the /memory slash command's job), saving session-specific task state (memory is for cross-session learning), or recording git history or code patterns that are derivable from the repo.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 61 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.

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.