Consistent meeting notes
Give every meeting summary the same structure, no matter who writes it.
Department
General
See all use cases
A post-meeting summary is the write-up that turns a conversation into something the rest of the company can act on: what was discussed, what was decided, and what happens next. Its value depends on structure as much as content; a reader who wasn't in the room needs to find the decision and the next steps without reading a transcript.
Every meeting summary looks different
Today, whoever writes a summary decides its shape: some list every topic in the order it came up, some bury the decision in the texts, some skip next steps entirely. A reader who wasn't in the meeting has to identify where to look before they can find what changed. The quality of a summary depends entirely on who was responsible for writing it that day, which affects downstream actions and results.
Qontext stores a shared meeting-notes skill
In Qontext, the format for a post-meeting summary is written once as a skill: the sections it must have, their order, and the level of detail expected. The skill lives in the context repository, so anyone installs it with qontext skills add <link> and keeps it current with qontext skills sync. Whichever agent drafts the write-up, for whichever meeting, it reads the same skill and produces a summary with the same structure. With Qontext, a reader who wasn't part of the meeting knows exactly where to find the decision and the next steps.
Get started
Write a skill in the Qontext workspace that defines the meeting-notes format: required sections, order, and level of detail.
Save it to the context repository and share it with an install link.
Others add it with
qontext skills add <link>and keep it current withqontext skills sync, so every summary an agent drafts follows the same structure.