Agent skill · operations · borghei
meeting-analyzer
Turn meeting notes into an accountable register — extract decisions, actions and open questions, flag ownerless items, track follow-through. Use when commitments get dropped or a recurring meeting decides nothing.
Why this skill is useful
Adds a structured method for extracting and tracking accountability from meeting notes, which the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Meeting Analyzer Meetings fail at the seam between talking and tracking. The decision gets made and nobody records who approved it; the action gets stated and nobody's name lands on it; the same topic returns for the seventh week because discussing it feels productive and deciding it feels risky. This skill closes that seam with deterministic extraction — pattern rules, no model calls — and then follows the commitments across meetings to see which ones actually close. Scope note This is the accountability lens on meetings, not the summary lens. It extracts and tracks; it does not write the polished recap. Use it on notes that already exist, across a series, when the question is "did anything we said we would do actually happen?" When to use this skill Actions keep getting dropped — items agreed in one meeting quietly reappear three weeks later, or never do A recurring meeting feels pointless — you need decision density and topic churn measured before proposing to cancel it Notes exist but no register does — months of markdown notes with decisions buried in prose that nobody can find or count The same topic returns every week — you need evidence of churn to force a decision owner and a deadline Preparing a retro or a meeting audit — completion rates and ageing per meeting show which rituals produce work that gets done Onboarding onto an existing project — extracting the decision log from past notes reconstructs why the system looks the way it does Inputs the skill expects Meeting notes or transcripts as markdown or plain text, one file per meeting Ideally several meetings from the same series, so trends are visible An action-item register with created date, due date, owner, status and carry-over count (the parser bootstraps this from notes) Per-occurrence series data: attendance, duration, decisions, actions, whether an agenda was posted and notes published, and the topics covered The reference date for ageing calculations, if not "the newest date in the data" Which …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/meeting-analyzer