CommunityProductivity & Collaborationgithub.com

weixilaw/meeting-minutes-agent

Converts messy meeting recordings, voice transcripts, and chat logs into structured, actionable meeting minutes. Trigger when the user sends raw meeting notes or transcripts and says "organize into minutes."

What is meeting-minutes-agent?

This skill transforms unstructured meeting notes, voice transcripts, or chat logs into professional, structured meeting minutes that are both actionable and traceable. It extracts a skeleton (topic, time, attendees, recorder) from the original text, categorizes content into 'Decided', 'Under Discussion', and 'Information Sync' (never mixing them), and generates clear action items with assigned owners, deadlines, and acceptance criteria. The skill enforces strict rules: no fabricating details (mark missing info as 'Not Recorded'), no omitting any decisions or tasks, and writing action items in verb-object format for clear executability. It supports multiple platforms (e.g., Claude Code, Cursor) and is ideal for teams wanting to turn verbal discussions into structured, trackable outputs.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/weixilaw/chinese-agent-skills/tree/HEAD/skills/meeting-minutes

Installed? Explore more Productivity & Collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Meeting Minutes Organization

Organizes raw meeting records provided by the user into actionable, traceable meeting minutes.

Organization Process

  1. Extract Skeleton: Meeting topic, time, attendees, recorder (if not in the original, mark as "Not recorded").
  2. Categorize Content: Divide content into "Decided" (settled matters), "Under Discussion" (disagreements not yet settled), and "Information Sync" (items merely informed). Never mix these categories.
  3. Extract Action Items: Each action item must have an owner + deadline + acceptance criteria. If any of the three is missing, mark it as "To be clarified" in the minutes.
  4. Output Minutes: Deliver in the format below.

Hard Rules

  • No Fabrication: If the original does not mention something, write "Not specified / Not recorded". Never imagine an owner or time.
  • No Omission: All decisions and action items must be fully included. Better a longer document than missing an item.
  • Actionable: Action items must use verb-object structure (one sentence clearly stating what to do). Avoid vague terms like "follow up" or "implement" – specify exactly what to follow up on and what the deliverable is.
  • Document Disagreements: Items with unresolved disputes must be listed separately under "To Be Confirmed", including each party's viewpoint and the next decision deadline.

Output Format

# Meeting Minutes: <Topic>
- Time: <Time/Not recorded> | Attendees: <List/Not recorded> | Recorder: <Person/Not recorded>

## Decided Items
1. …

## Action Items
| Task | Owner | Deadline | Acceptance Criteria |
|---|---|---|---|
| …… | …… | …… (mark "To be clarified" if unspecified) | …… |

## To Be Confirmed / Disagreements
1. …… (each party's viewpoint + planned decision time)

## Information Sync
- …

Boundaries

  • If the original contains multiple meetings mixed together, first split by topic, output separate minutes, and note the split.
  • If the user requests a "short version," retain only the Decided and Action Items, omitting the Information Sync section.

Individual skills in this repo

This repo contains 3 individual skills — each has its own dedicated page.

Related Skills