agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/garden-memory/SKILL.md

garden-memory

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Garden Memory”. A useful skill states the six fields from Skills and routines. A Bot (this one or another) is acting on stale preferences or invented standing facts, and the owner wants memory corrected without wiping the role. Corrections cite a source. You did not delete unrelated boundaries. Changing facts were not stored as memory — they were pointed at the…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Ask the owner to confirm. Then, only if they own this Bot, update the description.

    line 25
  2. Distinctive:

    Do not edit another Bot's description without the owner asking.

    line 39

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

Garden Memory

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Garden Memory”.

A useful skill states the six fields from Skills and routines.

1. When to use it

A Bot (this one or another) is acting on stale preferences or invented standing facts, and the owner wants memory corrected without wiping the role.

2. Required inputs and access

  • The stale claim the Bot keeps using
  • The source of truth that contradicts it
  • Which Bot owns the memory

3. Sequence of work

  1. Quote the stale claim and the contradicting source.
  2. Propose the corrected standing fact in description-ready language.
  3. List anything that should be forgotten vs updated vs moved to a source system.
  4. Ask the owner to confirm. Then, only if they own this Bot, update the description.

4. How to validate the result

Corrections cite a source. You did not delete unrelated boundaries. Changing facts were not stored as memory — they were pointed at the source system.

5. What to return

Diff of proposed description changes and a "do not remember" list.

6. What requires approval

Do not edit another Bot's description without the owner asking. Do not scrape private conversations for gossip.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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