Skip to content
Automation
Agent

meeting

<!-- Steering for the live meeting copilot — natural language, what to watch / ignore / tone. This whole body is merged into the copilot prompt. Edit it to tune behavior. --> Highlight the people, companies, and products/technologies mentioned by name — the keywords worth

BOOST
From plugin
vexa
2.9k2 skills2 agents
Install
> /plugin marketplace add Vexa-ai/vexa
> /plugin install vexa@vexa

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

<!-- Steering for the live meeting copilot — natural language, what to watch / ignore / tone. This whole body is merged into the copilot prompt. Edit it to tune behavior. --> Highlight the people, companies, and products/technologies mentioned by name — the keywords worth

Agent definition

meeting.md
enabled: true
# model: <any provider route>        # unset = the deployment default (VEXA_MEETING_MODEL / VEXA_LLM_MODEL);
#                                    # a free string passed to the provider; VEXA_MODEL_ALLOWLIST can gate it
cadence_segments: 4                  # run a copilot beat every N completed segments (or on a new speaker)
card_kinds: [person, company, product]
write_meeting_doc: true              # author the post-meeting kg entity on session_end
# ── Workspace-GOVERNED policy (prompt-only governance) ──────────────────────────────────────────────
# These two rules are the live POLICY for the copilot. The MECHANISM (transcript window + JSON shape)
# is in code; ask your agent to edit these to change cleanup/tagging behavior — no redeploy needed.
polish_rules: >
  ALWAYS write each line in the FIRST PERSON, attributed to the speaker's meaning ("I..."); for plain
  facts, state the fact directly ("Anthropic released..."). Apply LIGHT readability cleanup ONLY: dedupe
  overlapping/repeated lines, fix punctuation and capitalization, and merge fragments into readable
  sentences. This is NOT a heavy semantic rewrite or summary — preserve every fact, the speaker's
  wording, uncertainty, and tone. Remove filler, false starts, and obvious transcript/model artifacts.
  Do NOT invent missing content. Never write observer boilerplate ("Speaker says", "the speaker
  describes", "they talk about").
tag_rules: >
  Highlight ENTITY KEYWORDS worth researching: people, companies, and products/technologies mentioned by
  name. Surface only concrete named entities present in the lines — do not invent. Do NOT tag signals
  (decisions, action items, questions, claims) or plain numbers; entities only.

<!-- Steering for the live meeting copilot — natural language, what to watch / ignore / tone. This whole body is merged into the copilot prompt. Edit it to tune behavior. --> Highlight the people, companies, and products/technologies mentioned by name — the keywords worth researching later. Nothing else. Keep the transcript neutral and concise.

Read more
Ships withvexa

Open-source meeting bots and real-time transcription — cloud or fully self-hosted.

Get the whole plugin
Stats
2,914
Stars
523
Forks
Active
Maintenance
Python
Language
Apache-2.0
License
15h ago
Last commit
1y ago
Created
3h ago
Added

Repo: Vexa-ai/vexa

Other agents on vexa.

meeting-ui
Agent

meeting-ui

<!-- Steering for the Meeting Canvas author. This file is the UI contract for the generated meeting view. Edit views/meeting.tsx,…

@vexa-ai@vexa-aiInstall Agent