meeting-minutes

Name: meeting-minutes
Author: github

9.5kinstalls4.6kforks

How to install meeting-minutes?

github/awesome-copilot/meeting-minutes

$npx -y skills add github/awesome-copilot --skill meeting-minutes

Installs into the current project.

Summary

Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.

Files · 1

View on GitHub

SKILL.md

1	# Meeting Minutes Skill — Short Internal Meetings
2
3	## Purpose / Overview
4
5	This Skill produces high-quality, consistent meeting minutes for internal meetings that are 60 minutes or shorter. Output is designed to be clear, actionable, and easy to convert into task trackers (e.g., GitHub Issues, Jira). The generated minutes prioritize decisions and action items so teams can move quickly from discussion to execution.
6
7	## When to Use
8
9	Use this skill when:
10
11	- Internal syncs, standups, design reviews, triage, planning or ad-hoc meetings with short duration
12	- Situations that require a concise record of decisions, assigned action items, and follow-ups
13	- Creating a standardized minutes document from a live meeting, transcript, recording, or notes
14
15	---
16
17	## Operational Workflow
18
19	### Phase 1: Intake (before drafting)
20
21	- Obtain meeting metadata: title, date, start/end time (or duration), organizer, and intended audience.
22	- Confirm available inputs: agenda, slides, recording, transcript, or raw notes.
23	- If key details are missing, ask up to 3 clarifying questions before producing minutes (see "Discovery" below).
24
25	### Phase 2: Capture (during / immediately after meeting)
26
27	- Record attendees and absentees.
28	- Capture brief notes per agenda item with time markers if available.
29	- Record explicit decisions, rationale summary (1–2 sentences), and action items (owner + due date).
30
31	### Phase 3: Drafting
32
33	- Generate minutes following the Strict Minutes Schema (below).
34	- Ensure every action item includes owner, due date (or timeframe), and acceptance criteria when applicable.
35	- Mark unresolved issues or items requiring follow-up in the Parking Lot.
36
37	### Phase 4: Review & Publish
38
39	- If possible, send draft to meeting organizer or a designated reviewer for quick verification (within 24 hours).
40	- Publish final minutes to the agreed channel (shared drive, repo, ticket, or email) and optionally create tasks in the team's tracker.
41
42	---
43
44	## Discovery (required clarifying questions)
45
46	Before generating minutes, the agent MUST ask up to three clarifying questions if any of these are missing:
47
48	- What is the meeting title, date, start time (or duration), and organizer?
49	- Is there an agenda or transcript/recording to reference? If yes, please provide.
50	- Who should be assigned as the reviewer or approver for the minutes?
51
52	If the user responds "no transcript" or "no agenda," proceed but mark source material as "ad-hoc notes" and flag potential gaps.
53
54	---
55
56	## Strict Minutes Schema (Output Structure)
57
58	You MUST produce meeting minutes following this exact structure. If information is unavailable, use `TBD` or `Unknown` and explain how to obtain it.
59
60	### 1. Metadata
61
62	- Title:
63	- Date (YYYY-MM-DD):
64	- Start Time (UTC):
65	- End Time (UTC) or Duration:
66	- Organizer:
67	- Location / Virtual Link:
68	- Minutes Author (agent or person):
69	- Distribution List (who receives the minutes):
70
71	### 2. Attendance
72
73	- Present: [list of names + roles]
74	- Regrets / Absent: [list]
75	- Notetaker / Recorder: [name or "agent"]
76
77	### 3. Agenda
78
79	Bullet list of agenda items, in order:
80
81	- Item 1: short title
82	- Item 2: short title
83	- ...
84
85	### 4. Summary
86
87	A concise one-paragraph summary (1–3 sentences) of the meeting's objective and high-level outcome.
88
89	### 5. Decisions Made
90
91	Each as a separate bullet:
92
93	- Decision 1: statement of decision.
94	- Who decided / approved: [name(s) or group]
95	- Rationale (1–2 sentences): brief reason.
96	- Effective date (if applicable): YYYY-MM-DD
97	- Decision 2: ...
98
99	### 6. Action Items
100
101	Table-style bullets; must include owner and due date:
102
103	- [ID] Action: short description
104	- Owner: Name (team)
105	- Due: YYYY-MM-DD or "ASAP" / timeframe
106	- Acceptance Criteria: (what completes this action)
107	- Linked artifacts / tickets: (optional URL or ticket id)
108
109	Example:
110
111	- [A1] Draft deployment runbook for feature X
112	- Owner: Alex (Engineering)
113	- Due: 2026-02-05
114	- Acceptance Criteria: runbook includes steps for rollback, health checks, and monitoring links
115	- Linked artifacts: https://github.com/owner/repo/issues/123
116
117	### 7. Notes by Agenda Item
118
119	Brief, factual, timestamp optional:
120
121	- Agenda Item 1: title
122	- Key points:
123	- Point A (timestamp 00:05)
124	- Point B (timestamp 00:12)
125	- Open issues / questions:
126	- Q1: question text (owner if assigned)
127	- Agenda Item 2: ...
128
129	### 8. Parking Lot / Unresolved Items
130
131	- Item: short description
132	- Why parked / next step:
133	- Suggested owner or next meeting to resolve
134
135	### 9. Risks / Blockers (if any)
136
137	- Risk 1: short description, impact, mitigation owner
138	- Risk 2: ...
139
140	### 10. Next Meeting / Follow-up
141
142	- Proposed date/time (if any)
143	- Objectives for next meeting
144
145	### 11. Attachments / References
146
147	- Agenda

People who liked this also viewed

6 picks

Type

meeting-minutes

9.5kinstalls4.6kforks

View on GitHub

How to install meeting-minutes?

github/awesome-copilot/meeting-minutes

$npx -y skills add github/awesome-copilot --skill meeting-minutes

Installs into the current project.

Summary

Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.

Files · 1

View on GitHub

SKILL.md

1	# Meeting Minutes Skill — Short Internal Meetings
2
3	## Purpose / Overview
4
5	This Skill produces high-quality, consistent meeting minutes for internal meetings that are 60 minutes or shorter. Output is designed to be clear, actionable, and easy to convert into task trackers (e.g., GitHub Issues, Jira). The generated minutes prioritize decisions and action items so teams can move quickly from discussion to execution.
6
7	## When to Use
8
9	Use this skill when:
10
11	- Internal syncs, standups, design reviews, triage, planning or ad-hoc meetings with short duration
12	- Situations that require a concise record of decisions, assigned action items, and follow-ups
13	- Creating a standardized minutes document from a live meeting, transcript, recording, or notes
14
15	---
16
17	## Operational Workflow
18
19	### Phase 1: Intake (before drafting)
20
21	- Obtain meeting metadata: title, date, start/end time (or duration), organizer, and intended audience.
22	- Confirm available inputs: agenda, slides, recording, transcript, or raw notes.
23	- If key details are missing, ask up to 3 clarifying questions before producing minutes (see "Discovery" below).
24
25	### Phase 2: Capture (during / immediately after meeting)
26
27	- Record attendees and absentees.
28	- Capture brief notes per agenda item with time markers if available.
29	- Record explicit decisions, rationale summary (1–2 sentences), and action items (owner + due date).
30
31	### Phase 3: Drafting
32
33	- Generate minutes following the Strict Minutes Schema (below).
34	- Ensure every action item includes owner, due date (or timeframe), and acceptance criteria when applicable.
35	- Mark unresolved issues or items requiring follow-up in the Parking Lot.
36
37	### Phase 4: Review & Publish
38
39	- If possible, send draft to meeting organizer or a designated reviewer for quick verification (within 24 hours).
40	- Publish final minutes to the agreed channel (shared drive, repo, ticket, or email) and optionally create tasks in the team's tracker.
41
42	---
43
44	## Discovery (required clarifying questions)
45
46	Before generating minutes, the agent MUST ask up to three clarifying questions if any of these are missing:
47
48	- What is the meeting title, date, start time (or duration), and organizer?
49	- Is there an agenda or transcript/recording to reference? If yes, please provide.
50	- Who should be assigned as the reviewer or approver for the minutes?
51
52	If the user responds "no transcript" or "no agenda," proceed but mark source material as "ad-hoc notes" and flag potential gaps.
53
54	---
55
56	## Strict Minutes Schema (Output Structure)
57
58	You MUST produce meeting minutes following this exact structure. If information is unavailable, use `TBD` or `Unknown` and explain how to obtain it.
59
60	### 1. Metadata
61
62	- Title:
63	- Date (YYYY-MM-DD):
64	- Start Time (UTC):
65	- End Time (UTC) or Duration:
66	- Organizer:
67	- Location / Virtual Link:
68	- Minutes Author (agent or person):
69	- Distribution List (who receives the minutes):
70
71	### 2. Attendance
72
73	- Present: [list of names + roles]
74	- Regrets / Absent: [list]
75	- Notetaker / Recorder: [name or "agent"]
76
77	### 3. Agenda
78
79	Bullet list of agenda items, in order:
80
81	- Item 1: short title
82	- Item 2: short title
83	- ...
84
85	### 4. Summary
86
87	A concise one-paragraph summary (1–3 sentences) of the meeting's objective and high-level outcome.
88
89	### 5. Decisions Made
90
91	Each as a separate bullet:
92
93	- Decision 1: statement of decision.
94	- Who decided / approved: [name(s) or group]
95	- Rationale (1–2 sentences): brief reason.
96	- Effective date (if applicable): YYYY-MM-DD
97	- Decision 2: ...
98
99	### 6. Action Items
100
101	Table-style bullets; must include owner and due date:
102
103	- [ID] Action: short description
104	- Owner: Name (team)
105	- Due: YYYY-MM-DD or "ASAP" / timeframe
106	- Acceptance Criteria: (what completes this action)
107	- Linked artifacts / tickets: (optional URL or ticket id)
108
109	Example:
110
111	- [A1] Draft deployment runbook for feature X
112	- Owner: Alex (Engineering)
113	- Due: 2026-02-05
114	- Acceptance Criteria: runbook includes steps for rollback, health checks, and monitoring links
115	- Linked artifacts: https://github.com/owner/repo/issues/123
116
117	### 7. Notes by Agenda Item
118
119	Brief, factual, timestamp optional:
120
121	- Agenda Item 1: title
122	- Key points:
123	- Point A (timestamp 00:05)
124	- Point B (timestamp 00:12)
125	- Open issues / questions:
126	- Q1: question text (owner if assigned)
127	- Agenda Item 2: ...
128
129	### 8. Parking Lot / Unresolved Items
130
131	- Item: short description
132	- Why parked / next step:
133	- Suggested owner or next meeting to resolve
134
135	### 9. Risks / Blockers (if any)
136
137	- Risk 1: short description, impact, mitigation owner
138	- Risk 2: ...
139
140	### 10. Next Meeting / Follow-up
141
142	- Proposed date/time (if any)
143	- Objectives for next meeting
144
145	### 11. Attachments / References
146
147	- Agenda

People who liked this also viewed

6 picks

Type