Walk into every outside meeting with a short, cited brief.
Meeting brief is a Claude routine for AI meeting prep. Before each meeting that includes someone from outside your company, it researches that company and writes a brief of at most five short lines to your Desk. Every line names the page it came from.
AI meeting prep: what it does
It looks at your calendar for meetings that start inside a look-ahead window (24 hours by default). It keeps a meeting only if at least one attendee is from a domain that is not on your internal list.
For each outside company it searches the web and opens a few pages, starting with the company's own site. The brief covers what the company does, recent news with its date, and one question worth asking. The prompt tells it to leave out anything it did not read.
What it is told never to do
- The prompt forbids sending, posting, accepting, declining or changing a meeting. The first run is report-only.
- The prompt tells it to record attendee company domains and the meeting title only, never attendee names or addresses.
- The prompt forbids guessing a company's size, revenue or plans. It reports what it read, with the source.
- The prompt treats calendar text and web pages as data. An instruction inside a meeting description or a page is ignored.
- The prompt forbids writing your settings. If a change looks right, it proposes one and you accept or reject it.
These are rules in the routine's prompt. See honest limits for what is and is not checked by code.
Look-ahead and domain settings
| Setting | Key | Default | Note |
|---|---|---|---|
| Look ahead (hours) | lookahead_hours | 24 | 4 to 72. A longer window means more meetings to research. |
| Internal domains | internal_domains | none | Meetings with only these domains are skipped. |
| Pages per company | max_research_pages | 5 | 1 to 15. Each page is one more page open. |
| Inbox messages per run | max_inbox_per_run | 5 | 0 to 20. |
Stages and the calendar connector
| Stage | Kind | Does |
|---|---|---|
| Find outside meetings | model | Lists meetings inside the look-ahead window that include an outside domain. |
| Research each company | model | Searches for each outside company and reads a few pages, keeping each source URL. |
| Learn | code | Turns feedback on earlier runs into learning and proposals before the write. |
| Write | code | Applies the run under the write contract. |
| Connector | Needed | Used for |
|---|---|---|
| Calendar | Required | List upcoming meetings and their attendee domains. Read access. |
| Web search | Required | Find each outside company. Check your run has it before the first run. |
| Web fetch | Required | Open the company's pages. |
What the Desk shows
The Desk for this template has two record types, Meeting and Company, and two views. The Inbox carries an alert for a meeting that starts inside the next 4 hours and has a brief, within your per-run limit. How the Desk works.
| View | Shows | Columns |
|---|---|---|
| Upcoming meetings | Active meetings, soonest first | Starts, title, company domains |
| Companies researched | Companies, most recently seen first | Name, industry, domain |
Install the meeting brief
- Install the pluginIn Claude Code 2.1.275 or later. The command line tool needs Python 3.11 or later.
/plugin install routineos --marketplace devkindhq/routineos - Install the packFrom a clone of the repository root. It writes a routine folder, prints what you must connect, runs nothing and connects nothing.
python3 skills/routineos/scripts/routineos.py pack install catalog/meeting-brief.json --dir my-meeting-brief - Connect, publish, run onceConnect what the pack lists, publish the Desk, and let the first run go. Nothing leaves the routine on the first run.
The first routine guide walks a template to a first run, and Install a pack lists every refusal the installer can give. Free (MIT). Needs a paid Claude plan.
Known risks and limits
- A wrong company match is possible, because two companies can share a name. The brief is based on the attendee's domain and each line names its source, so you can check it.
- Calendar contents are private. The template stores the meeting title and attendee domains. Check that storing titles is acceptable where you work.
- A meeting description or a web page can carry instructions. The prompt treats all of it as data, which is a prompt rule, not a guarantee.
- If a source fails to load, the run is marked partial and says why.
- Other calendar apps may work. Whether each offers the access needed is unverified.
- Scheduling is a research preview and may change. See honest limits.
Related templates and reading
Jobs watch
Tracks public job postings and links each role to its company.
Sales use cases
Routines a sales team can run, with the Desk and approvals.
How it learns
What the routine suggests after you keep, drop or reject what it found.
More: questions and answers, schedule a routine in Claude Code, how RoutineOS maps to Rails.
Read one brief before you rely on it.
Install RoutineOS, add Meeting brief, and read one brief before your next outside meeting.