Skip to content

Unofficial community registry. Not affiliated with, endorsed by, or sponsored by xAI.

中文

Templates

Memory layout

memory-layout

Four headings: facts, preferences, open loops, last run. There is no fifth pile.

for Grok Bot · unofficial, not affiliated with xAI

CNPS0.1.02026-11-18New

Paste this template into Grok Bot and say: start from this template. Replace the blanks first.

Template: Memory layout
Four headings: facts, preferences, open loops, last run. There is no fifth pile.

For: People setting up the file from Keep memory for the next run.

# Facts
(short lines you can point to)

# Preferences
(output language, directories, what it should not do)

# Open loops
(one item per line)

# Last run
Time:
What happened:

Do not add headings for secrets, full emails, or payment.

Setup:
1. Copy it to memory/bot.md.
2. Write the first line under each heading in your working language.
3. Point the memory skill at these four headings only.
4. A person decides when an old fact goes. The skill does not delete it.

Do not:
- Do not store secrets, full letters, or payment details in this file.
- Do not commit the file to a public repository once it holds customer facts.
- Do not let a skill delete an old fact on its own.

Paste this template into Grok Bot and say: start from this template. Replace the blanks first.

What it does

  • Fixes four headings.
  • Keeps last run to a time and one sentence.
  • Leaves no place for a secret.

Who it is for

People setting up the file from Keep memory for the next run.

How to put it in Grok Bot

  1. Copy it to memory/bot.md.
  2. Write the first line under each heading in your working language.
  3. Point the memory skill at these four headings only.
  4. A person decides when an old fact goes. The skill does not delete it.

Example

Template

# Facts
(short lines you can point to)

# Preferences
(output language, directories, what it should not do)

# Open loops
(one item per line)

# Last run
Time:
What happened:

Do not add headings for secrets, full emails, or payment.

Connectors it needs

No connector.

Safety and permissions

  • Do not store secrets, full letters, or payment details in this file.
  • Do not commit the file to a public repository once it holds customer facts.
  • Do not let a skill delete an old fact on its own.

Risk: Low

Questions

I want a Customers heading.

Put a customer fact under facts and name the customer. Extra headings make the next read unsure.

How long is last run?

One sentence. The detail lives in that day's output file.