Skip to content

Capabilities

Context

Context is what MAIA remembers between runs. Skills hold your method, and knowledge holds what MAIA should know about you and your work.

Why it matters#

Context is what makes Compound work. A skill carries your method to the next county. Knowledge carries your context to the next project. A run starts better when MAIA already knows how you work and who you are.

Two kinds of context#

Those are two different things, and MAIA stores them apart.

HoldsSkillsA method: criteria, thresholds, steps, and output formatKnowledgeContext: your business, your markets, your terms
AnswersSkillsHow do we do this?KnowledgeWho is asking?
LoadedSkillsWhen a run needs itKnowledgeThe core file on every turn, other entries when a run needs them
Tied to a placeSkillsNo. A skill runs in any county, so it must not name oneKnowledgeProject knowledge is. It ends with the project
Read moreSkillsSkillsKnowledgeKnowledge

Scopes side by side#

Both are scoped. The scope decides who can see an entry and where MAIA uses it.

PersonalSkillsPrivate to you, in every projectKnowledgePrivate to you, in every project
WorkspaceSkillsEveryone in the workspace can run itKnowledgeEveryone in the workspace, on every turn
ProjectSkillsNoneKnowledgeProject memory, which lives and ends with the project
SystemSkillsMAIA's ready-made skills, which are read-onlyKnowledgeNone

How context reaches a run#

Only the core knowledge files load on every turn, one per scope. Everything else waits until a run asks for it: MAIA sees one line per skill, a name and a description, and loads a skill's full instructions only when a run calls for it. That keeps a run focused on the question in front of it.

Three things follow:

  • What you put in a core file costs attention on every run. Keep it to what is true of all your work.
  • A skill that names a county or city will not carry to the next county. Leave the place out.
  • MAIA saves a lasting fact to knowledge on its own when you state one. Read what it holds from time to time.

In the app and over MCP#

Both kinds live under your account, on the Knowledge & skills tab. A project's own memory is on the project's Project memory tab. Over MCP, list_skills and save_skill handle skills, and save_to_maia_memory writes knowledge. The teach_maia prompt fills in a profile of your work. See Tools and Prompts.

In this section