Work with memory and skills

Memory stores durable facts and preferences. Skills store reusable procedures. Both can be personal, team-scoped, or corporate, but those scopes have different approval and isolation requirements.

Use memory for durable context

Good memory is specific, stable, and useful in future conversations. Examples include an approved project convention, a user's persistent preference, or a team glossary.

Avoid storing:

• API keys, passwords, tokens, or private authentication material;
• temporary task state that belongs in the current session;
• unverified claims presented as company policy;
• personal information outside the intended identity scope.

Use skills for repeatable work

A skill should describe when it applies, the procedure to follow, required tools or configuration, validation, and common failure modes. Keep a skill focused enough that Maia can decide reliably when to use it.

Choose the correct scope

Need	Correct scope
One gateway user's preference	User memory
A department procedure	Team skill, after approval
A company-wide naming rule	Corporate memory, after approval
A local developer experiment	Local profile memory or skill

Verify user isolation

1. Create a harmless personal memory with user A.
2. Confirm user A can recall it in a new session.
3. Ask user B about the same information.
4. Confirm the personal memory is not available to user B.
5. Repeat with an approved team memory to verify that only assigned team members receive it.