meeting-notes

Installation
SKILL.md

Meeting Notes

Two leading words control every step:

  • Source-bound: every name, date, decision, reason, owner, due date, and priority comes from the source. When the source does not give a value, write a marker (Unassigned, No date, Not stated) and add a clarifying question. Tag a value you suggest (proposed).
  • Anchor: the place in the source that shows an item: the timestamp when the source has one, else the speaker and a short quote. Each decision and action item carries one, unless the user asks to leave anchors out.

Step 1: Gather Inputs

Ask once, in one message, for the items the request does not give:

  • Source: pasted text or a file path, and its type: transcript, human notes, or AI summary (Zoom, Meet, Teams, Otter, and others). An AI summary is a set of claims, not the record: ask for the transcript when the user has it.
  • Meeting: title, date, attendees and their handles
  • Meeting type: general, standup, client call, project review, formal minutes (board, committee, council), or other
  • Output style: terse bullets or narrative; detail level (executive, standard, detailed); focus (comprehensive, action items only, decisions only); action-item format (checkboxes or table); redaction rules

Done when you have the source and know its type. For each other item the user does not give, use the default: the date from the source or No date, the type the content shows, terse bullets, standard detail, comprehensive focus, checkboxes.

Step 2: Normalize the Source

Installs
1
GitHub Stars
1
First Seen
Oct 21, 2026
Security Audits