Skip to main content
Memory and skills solve different problems.
  • Memory stores stable facts and preferences.
  • Skills store reusable process.
Use both when you want companions to improve without long prompts.

​
Put facts in memory

Good memory:
Avoid:
That is a task, not durable memory.

​
Put process in skills

Good skill:
Avoid putting this process in memory unless it is a stable preference and not an executable workflow. When a companion completes a repeatable workflow well, ask it to save the process while the details are fresh:

​
Keep both scoped

Use companion-specific memory and skills when only one companion should use the context. Use global or shared memory and skills when all relevant companions should use them.

​
Maintain over time

Review memory and skills when:
  • Your product changes.
  • Your ICP changes.
  • You change tone or messaging.
  • A routine starts producing noisy results.
  • A companion repeats outdated assumptions.

​
Ask Strawberry to help maintain them

Useful prompt:
If the same workflow should run on a schedule, create a routine instead:

​
Safety

Do not store secrets, credentials, personal data, or confidential customer data in memory or skills unless the scope is correct and there is a clear reason.