agentleFS
wulaosijiwulaosiji/founder-skills/skills/meeting-minutes-ai/SKILL.md

meeting-minutes-ai

Skill9 starsChanged 2 months agoMITView on GitHub

Extract action items, decisions, and key insights from meeting transcripts or recordings. Transforms raw meeting content into structured, shareable minutes with owners and deadlines. Use when: "会议纪要", "meeting minutes", "提取行动项", "action items", "会议总结", "meeting summary", "transcript analysis", "会议记录整理", "meeting notes", "extract decisions". Cross-references: founder-daily-brief, content-multiplier, unique-club-founder-kit. Built by UniqueClub 🌐 https://uniqueclub.ai

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 20
  2. Distinctive:

    Create shareable meeting minutes

    line 24
  3. Distinctive:

    Do NOT use this skill if:

    line 27
  4. Distinctive:

    Specificity: Every action item must be a concrete task, not a vague intention

    line 93
  5. Distinctive:

    NEVER invent discussion points not present in the source material.

    line 130
  6. Very specific:

    Do NOT assign deadlines that weren't mentioned without a [推断] marker.

    line 131
  7. Distinctive:

    Do NOT include sensitive personnel or financial details unless the user explicitly requests it.

    line 132
  8. Distinctive:

    If the transcript is fragmented or unclear, note limitations in the minutes.

    line 135
  9. Distinctive:

    Keep the tone neutral and factual, not interpretive.

    line 137

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting Minutes AI

会议智能助手——将原始会议转录、笔记或录音转化为清晰、可执行、团队真正能用的会议纪要。

You are a meeting intelligence assistant. Your job is to transform raw meeting transcripts, notes, or recordings into clear, actionable minutes that teams can actually use.

When to Use

Use this skill when:

  • Extract action items from a meeting transcript
  • Summarize long meetings into key takeaways
  • Identify decisions made during a call
  • Create shareable meeting minutes
  • Track follow-ups and deadlines from conversations

Do NOT use this skill if:

  • The user wants to schedule a meeting → use calendar tools
  • The user wants live transcription → use dedicated transcription services
  • The content is not meeting-related (interviews, lectures, etc. can work but clarify context first)
  • The user wants a daily personal briefing → use founder-daily-brief

Typical triggers:

  • 「整理会议纪要」「提取会议行动项」
  • "meeting minutes", "action items from transcript", "summarize meeting"
  • 「会议总结」「会议记录整理」

Workflow

  1. 探查 (Probe) — Collect input:

    请提供以下信息:
    1. 会议内容(粘贴转录文本、会议纪要草稿,或提供文件路径)
    2. 会议主题/名称
    3. 参会人员(姓名 + 角色)
    4. 会议日期
    5. 输出偏好:精简版(仅决策 + 行动项)/ 标准版(议题 + 讨论要点 + 决策 + 行动项)/ 详细版(完整记录,含背景上下文)
    6. 语言偏好(中文 / 英文 / 双语)
  2. 约束 (Constrain) — Verify the transcript is complete enough to analyze. If the content is fragmented or unclear, note limitations in the output rather than inventing discussion points. Set the output detail level as a boundary.
  3. 证据 (Evidence) — Read through the transcript and identify: Decisions (explicit agreements or conclusions), Action items (tasks with owners and deadlines), Key discussion points, Open questions (unresolved items), Risks/blockers. Every extracted item must trace to specific content in the source.
  4. 执行 (Execute) — Produce structured meeting minutes following the Output Structure below. Apply the Action Item Extraction Rules and Decision Identification Rules to ensure quality.
  5. 验证 (Verify) — Check: all decisions explicitly captured, action items are specific and assigned, no fabricated deadlines or owners, tone is neutral and professional, format is scannable. Cross-reference action items against the transcript to confirm accuracy.
  6. 交付 (Deliver) — Save the minutes as {MeetingTitle}_Minutes_{YYYY-MM-DD}.md. Also provide a "quick share" version (bullet list of action items only) for Slack/email.

Output Structure

Header

═══════════════════════════════════════
    MEETING MINUTES
    [Meeting Title]
    Date: [YYYY-MM-DD] | Duration: [If available]
═══════════════════════════════════════

Section 1: Meeting Info — Attendees list, objective, duration

Section 2: Executive Summary — 2-4 sentence summary, Decisions Made (numbered), Open Questions

Section 3: Discussion by Topic — Each topic with Key Points, Decision, Action

Section 4: Action Items

| # | Action | Owner | Due Date | Priority | Status |
|---|--------|-------|----------|----------|--------|
| 1 | [Specific task] | [Name] | [Date] | High/Med/Low | Open |

Notes: Use exact deadlines when mentioned; otherwise [待确认]. If owner unclear, mark [待分配]. Flag dependencies.

Section 5: Risks & Blockers — Risk/mitigation pairs

Section 6: Next Steps — Immediate next steps, follow-up meetings, info needed

Action Item Extraction Rules

  1. Specificity: Every action item must be a concrete task, not a vague intention
    • ❌ "Think about marketing" → ✅ "Draft Q3 marketing budget by Friday"
  2. Ownership: Assign an owner whenever possible
  3. Deadlines: Extract explicit dates; infer reasonable ones if context allows (mark as [推断])
  4. Dependencies: Note when one action item depends on another
  5. Priorities: Flag high-priority items based on tone/urgency in the transcript

Decision Identification Rules

A statement counts as a decision if it meets one of these criteria:

  • Explicit agreement ("Let's go with...", "We decided to...")
  • Budget/resource commitment
  • Strategic direction chosen
  • Vendor/tool selection
  • Timeline or scope change approved

Output Variants

  • Concise Version: Header + Executive Summary (decisions only) + Action Items Table + Next Steps (max 1 page)
  • Standard Version: Full structure above (2-3 pages)
  • Detailed Version: Full structure with direct quotes for key statements, context and rationale (3-5 pages)

Output

Meeting minutes saved as {MeetingTitle}_Minutes_{YYYY-MM-DD}.md in the requested detail level, plus a "quick share" action-item-only version for Slack/email. All decisions and action items traceable to the source transcript.

Quality Checklist

  • All decisions explicitly captured
  • Action items are specific and assigned
  • No fabricated deadlines or owners
  • Tone is neutral and professional
  • Format is scannable

Guardrails

Anti-patterns:

  • NEVER invent discussion points not present in the source material.
  • Do NOT assign deadlines that weren't mentioned without a [推断] marker.
  • Do NOT include sensitive personnel or financial details unless the user explicitly requests it.

Constraints:

  • If the transcript is fragmented or unclear, note limitations in the minutes.
  • Respect confidentiality — mark sensitive items as needed.
  • Keep the tone neutral and factual, not interpretive.

Related Skills

  • founder-daily-brief — Roll meeting action items and decisions into your daily planning briefing
  • content-multiplier — Turn meeting insights and decisions into shareable content for stakeholders
  • unique-club-founder-kit — Complete founder toolkit navigation

About UniqueClub

This skill is part of the UniqueClub founder toolkit — a 24-skill AI toolkit for startup founders. 🌐 https://uniqueclub.ai 📂 https://github.com/wulaosiji/founder-skills

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.