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: 
Our ICP is B2B SaaS companies with 50-500 employees in the Nordics.
Primary buyer titles are VP Sales, Head of RevOps, and Founder.
Avoid: 
Research these 12 companies by Friday.
That is a task, not durable memory.

​
Put process in skills

Good skill: 
When evaluating a prospect, inspect website, LinkedIn, funding news,
and CRM history. Score fit from 1-5 and cite evidence.
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: 
Create a skill for me from this workflow.
Ask me targeted questions if anything is missing before you save it.

​
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: 
Review this chat and suggest only durable facts that should be saved to memory.
Do not save temporary task details. Separate facts from workflow improvements
that belong in a skill.
If the same workflow should run on a schedule, create a routine instead: 
Do this workflow every Tuesday morning.
Ask me what trigger, approval rules, and notification rules you need.

​
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.