본문으로 건너뛰기
cccskills
무료GitHub에 공개

vexa-meetings

Use Vexa to send a bot to meetings, follow transcripts as conversations unfold, and create dated notes with speakers, decisions, and assigned actions. Search past discussions and organize meeting records with titles and metadata.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Work with the user's meetings through the Vexa MCP tools — send a bot to a call, follow the transcript while it runs, and write meetings into their notes (Obsidian, Notion, plain markdown) with speakers and action items. Use whenever the user mentions a meeting, a call, a transcript, meeting notes, or asks what was said.

연동 도구NotionObsidian

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Send a bot to a meeting and follow the live transcript
  • Save meeting notes in Obsidian, Notion, or Markdown
  • Find past discussions and decisions across meetings
  • Record decisions and action items with their owners

포함된 파일(2)

  • SKILL.md2.5 KB
  • README.md187 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Vexa meetings

The vexa MCP server is connected. Start with whats_waiting — it says what the user's Vexa needs right now.

Send a bot to a call

  1. parse_meeting_link(meeting_url) → platform + native_meeting_id.
  2. request_meeting_bot(meeting_url). A human in the call must admit the bot; expect a delay between requested and active.
  3. get_meeting_transcript(platform, native_meeting_id) while the meeting runs. Pass since_index to read only what is new. A meeting that is active with zero segments usually means the bot is not admitted yet or nobody has spoken.
  4. stop_bot(platform, native_meeting_id) when done.

Every tool returns platform + native_meeting_id; feed one tool's output straight into the next.

Write a meeting into the user's notes

When asked to sync, log, or file a meeting:

  • list_meetings (filters: status, platform, metadata) to find it; get_meeting_transcript for the segments; get_meeting_participants is not a tool — participants come from the segments' speaker names.
  • Write one note per meeting, dated, in the user's existing format if there is one (look at a recent note first). Include: title, date, participants (from speaker labels), a short summary, decisions, action items with owners, and the transcript or a link to it. Keep speaker labels as they are — do not guess names the transcript does not carry.
  • Ask before writing outside the folder the user named.

Search across meetings

search_transcripts returns ranked snippets of what was said, not whole transcripts. Use it for "what did we decide about X", then open the meeting for context.

Make the data durable

annotate_meeting attaches a title and metadata (a CRM id, a ticket, tags). Anything you put there is findable later with list_meetings(metadata_filter=...). If you learn something durable about a meeting, write it back.

Do not

  • Do not call speak_in_meeting unless the user asked for that exact thing to be said. It is audible to everyone present and irreversible.
  • Do not read a meeting's meetings_failed-style counters as reliability; a meeting ends in many states that are not errors.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Schedule recurring summaries, reports, checks, and reminders through routine files. Each file defines when the agent runs and what it does, creating a persistent Vexa Scheduler job that can be updated or disabled and survives restarts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Weekday summaries of yesterday’s meetings
  • Weekly report scheduling
  • Recurring checks
Vexa-ai/vexa2.9천2026년 10월 23일 업데이트

Connect an agent to Vexa through MCP, a connection interface for agent tools. Find the API key source, choose the hosted or self-hosted URL, and check whether connection failures come from authentication or an unavailable server.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Connect an agent to Vexa for the first time
  • Investigate a 401 authentication error
  • Configure a self-hosted Vexa connection URL
Vexa-ai/vexa2.9천2026년 10월 23일 업데이트

Vexa-ai의 스킬 모두 보기

이 스킬의 문제 신고