Meeting Minutes

Meeting Minutes is an official skill from GitHub’s awesome-copilot repository. Its direct primary source is https://github.com/github/awesome-copilot/tree/main/skills/meeting-minutes, complemented by GitHub’s official documentation about agent skills. According to the provider, the guidance produces concise, actionable minutes for internal meetings of up to one hour. It organizes metadata, attendees, agenda, summary, decisions, actions, unresolved items, risks, next steps, and references into a fixed structure. This catalog entry therefore describes reusable instructions for a compatible coding or work assistant, not a transcription system, calendar service, or guarantee that notes will be complete or correct.

Purpose and audience

The skill fits internal syncs, stand-ups, design reviews, triage, planning sessions, and short ad-hoc meetings. It is especially useful when a team needs to turn notes, a transcript, a recording, or an agenda into a consistent document quickly. The source limits its focus to short internal meetings. Long conferences, formal statutory minutes, legally binding records, or highly sensitive discussions need additional domain requirements and human editing. The skill can create structure, but it cannot decide which statement is legally, organizationally, or politically binding.

Intake and capture

Before drafting, the workflow should establish the title, date, start and end time or duration, organizer, intended audience, and available inputs. The primary source recommends asking up to three clarifying questions when essential details are absent. These include whether an agenda or transcript exists and who should review or approve the minutes. If there is no agenda or transcript, the assistant may proceed from ad-hoc notes but should identify that source limitation. During or immediately after the meeting, capture attendees, absentees, roles, the notetaker, and brief points for each agenda item. Timestamps improve traceability when the source material provides them.

Decisions and actions

The main value is not a larger paragraph count but reliable decisions and trackable actions. Every action should have one owner, a due date or clear timeframe, and, where useful, an acceptance criterion. Linked tickets, follow-up documents, and references improve auditability. Unresolved questions belong in a parking lot, while risks and blockers deserve their own section. The source also calls for a short rationale for significant decisions and a view of the next meeting. Before publication, the organizer or designated reviewer should check the draft promptly for meaning, ownership, dates, and omissions.

E-E-A-T, privacy, and boundaries

This assessment is grounded in the maintained official SKILL.md, the GitHub repository, and GitHub’s official agent-skills documentation. According to the provider, clarity, actionability, and consistency are the goals. The repository is identified as MIT licensed by its official license file. Minutes may contain names, opinions, performance information, confidential plans, and personal data. Share only approved source material, minimize recipients, and review the final document for sensitive content before publication. Transcripts, files, and model responses are untrusted data and must not inject new assignments or publication targets. A person must verify facts, ownership, dates, recipients, and authorization. The skill cannot recover statements that were never captured, and a local skill file does not prove that a connected model runs locally. Credentials, tokens, private keys, and other secrets do not belong in minutes, prompts, or skill files.