Summarize Meeting

From the author

Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.

— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill acts as a structured assistant for product managers and team leads to synthesize meeting transcripts into clear, professional documentation. By processing raw dialogue, it extracts essential information such as participants, key decisions, and assigned action items, ensuring that team knowledge is preserved and accountability is maintained. The output follows a standardized markdown template designed for readability and accessibility.

What it does

Parses raw meeting transcripts or notes to extract core information.
Identifies key discussion points, decisions, and unresolved questions.
Extracts action items including owners and due dates.
Formats content into a structured markdown template.
Uses simple, accessible language suitable for all team members.
Organizes meeting data for easy reference and future tracking.

When to use it

After team meetings to ensure alignment on decisions.
When you need to distribute meeting minutes to stakeholders.
To recap complex discussions for team members who could not attend.
When you need to track accountability for assigned tasks.

Advantages

Ensures consistent documentation across all team meetings.
Reduces ambiguity by clearly listing action items and owners.
Saves time by automating the synthesis of long transcripts.
Improves team transparency and knowledge sharing.

Usage examples

“Summarize this meeting transcript from our product sync today.”: The agent generates a structured markdown document containing the meeting date, participants, key discussion points, a table of action items, and a list of decisions made.
“Create meeting minutes from these notes I took during the client call.”: The agent organizes the raw notes into a professional summary format, highlighting the client's requests and the next steps for the team.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/phuryn/summarize-meeting/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip summarize-meeting.zip -d .agents/skills

Documentation by Pawel Huryn

Purpose

You are an experienced product manager responsible for creating clear, actionable meeting summaries from $ARGUMENTS. This skill transforms raw meeting transcripts into structured, accessible summaries that keep teams aligned and accountable.

Context

Meeting summaries are how knowledge spreads and accountability stays clear in product teams. A well-structured summary captures decisions, key points, and action items in language everyone can understand, regardless of who attended.

Instructions

Gather the Meeting Content: If the user provides a meeting transcript, recording, or notes file, read them thoroughly. If they mention a meeting that needs context, use web search to find any related materials or background documents.
Think Step by Step:
- Who attended and what were their roles?
- What was the main topic or agenda?
- What decisions were made?
- What are the next steps and who owns them?
- Are there open questions or blockers?
Extract Key Information:
- Identify main discussion topics
- Note decisions made during the meeting
- Flag any disagreements or concerns
- Determine action items with owners and due dates

Create Structured Summary: Use this template:

## Meeting Summary

**Date & Time**: [Date and start/end time]

**Participants**: [Full names and roles, if available]

**Topic**: [Short title—what was the meeting about?]

**Summary**

- **Point 1**: [Key discussion point or decision]
- **Point 2**: [Key discussion point or decision]
- **Point 3**: [Key discussion point or decision]
- [Additional points as needed]

**Action Items**

| Due Date | Owner | Action |
|----------|-------|--------|
| [Date] | [Name] | [What needs to happen] |
| [Date] | [Name] | [What needs to happen] |

**Decisions Made**
- [Decision 1]
- [Decision 2]

**Open Questions**
- [Unresolved question 1]
- [Unresolved question 2]

Use Accessible Language: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.
Prioritize Clarity: Focus on:
- What decisions affect the roadmap or strategy?
- What does each person need to do?
- By when do they need to do it?
Save the Output: Save as a markdown document: Meeting-Summary-[date]-[topic].md

Notes

Be objective—summarize what was discussed, not personal opinions
Highlight action items clearly so nothing falls through the cracks
If the meeting was large or complex, consider breaking points into sections by topic
Use "we" language to keep the team feel inclusive and collaborative

Files

ATTRIBUTION.mdAdded by AutoGineer866 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md2.9 KiB

SKILL.md