Meeting Analyzer

Turns meeting notes into an accountable register and diagnoses recurring meetings. Use when commitments get dropped or a series decides nothing; for a single meeting's recap use summarize-meeting.

1,157 stars 217 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add borghei/Claude-Skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add borghei/Claude-Skills --skill meeting-analyzer
Manual install
git clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skills/project-management/meeting-analyzer ~/.claude/skills/meeting-analyzer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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
Read the full skill on GitHub

Details

Skill name
meeting-analyzer
Path
project-management/meeting-analyzer/SKILL.md
Repo updated
8 November 2026

FAQ

What does the Meeting Analyzer skill do?

Turns meeting notes into an accountable register and diagnoses recurring meetings. Use when commitments get dropped or a series decides nothing; for a single meeting's recap use summarize-meeting.

How do I install the Meeting Analyzer skill?

Claude Code plugin: /plugin marketplace add borghei/Claude-Skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Meeting Analyzer popular?

It lives in borghei/Claude-Skills, which has 1,157 GitHub stars and 217 forks, and is included in 1 curated skill list.

Related skills

Cto Advisor

1.2k

borghei/Claude-Skills

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, or making architecture decisions.

Software DevelopmentIn 1 list217

Customer Success Manager

1.2k

borghei/Claude-Skills

Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success

Marketing, Sales & BusinessIn 1 list217

Financial Analyst

1.2k

borghei/Claude-Skills

Performs financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction for strategic decision-making

Finance & CryptoIn 1 list217

Meeting Insights

1.2k

borghei/Claude-Skills

Analyze meeting transcripts to extract decisions, action items, owners, due dates, open questions, and risks. Use after recorded meetings, sales calls, customer interviews, or planning sessions, or to build a decision log.

Productivity & NotesIn 1 list217

Ma Playbook

1.2k

borghei/Claude-Skills

M&A strategy for acquiring companies or being acquired. Use when evaluating acquisitions, preparing to be acquired, conducting due diligence, planning integration, or negotiating deal terms (valuation, LOI, earnout, deal structure).

Productivity & NotesIn 1 list217

Notion Pm

1.2k

borghei/Claude-Skills

Designs Notion databases, views and page structure for PRDs, OKRs, roadmaps and decisions, and writes REST API calls. Use when asked to "design a PRD database", sync Notion with Jira or Linear, or script the Notion API.

Productivity & NotesIn 1 list217

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.