Components

The skills

The framework itself. A skill cannot start a session — it is loaded into one.

The most common misunderstanding about this part is that it is a program.

It is not. A skill is a set of instructions loaded into a session that is already running. It cannot start anything, cannot run on a schedule, and cannot be called by another piece of software. Everything it does happens because a person opened a session and something was read into it.

That constraint is not a limitation being apologised for. It is the reason the rest of the architecture has the shape it does: anything that must start something is a tool, not a skill. Every component on this page that runs on demand or on a timer exists because a skill could not do that job, and drawing that line once meant not having to argue about it per feature.

What a skill actually holds

Not the logic for processing a meeting — a model can do that unprompted. What a skill holds is what a file means: that this folder’s _ops.yaml declares which chats belong to it, that a task in the ledger is owned by a person and not by the system, that a note carries its carry-forward or the next agenda is built on a lie.

That is why the framework is the one component that cannot be swapped out. Replace the transcription backend and the chain still works. Remove this and there is no chain, only a pile of files.

This part is public

It is MIT-licensed and installable. Most skills you invoke by name; two exist only to be read by the others. The skills page counts them from the contract, so the number is never typed here.

From ecosystem.yaml, contract 41 · core-skills 1.89.4 · read at build 2026-10-08