New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Meeting Minutes

by github in github/awesome-copilot

Generate concise, actionable meeting minutes for internal meetings.

OfficialMITAuto-check passedProductivity & Automation

Install Meeting Minutes

skills CLI
$ npx skills add github/awesome-copilot --skill meeting-minutes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot meeting-minutes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/meeting-minutes .claude/skills/meeting-minutes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
meeting-minutes
GitHub stars
40k
Used in
2 other repos
Token cost
~2k tokens
SKILL.md length
997 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Generate concise, actionable meeting minutes for internal meetings.

  • Works in 12 steps: Intake (before drafting) → Capture (during / immediately after… → Drafting → …
  • Tasks that involve Meeting notes and agendas
  • SKILL.md covers Purpose / Overview, When to Use, Operational Workflow and Discovery (required clarifying…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Meeting Minutes is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Meeting notes and agendas. It works with GitHub. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Tasks that involve Meeting notes and agendas

Example prompts

  • “/meeting-minutes”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Intake (before drafting)
  2. Capture (during / immediately after meeting)
  3. Drafting
  4. Review & Publish
  5. Metadata
  6. Attendance
  7. Agenda
  8. Summary
  9. Decisions Made
  10. Action Items
  11. Notes by Agenda Item
  12. Parking Lot / Unresolved Items

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Meeting Minutes loads about 2k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 997 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 997 words, ~1,969 tokens.

Download SKILL.mdSave it as .claude/skills/meeting-minutes/SKILL.md (or your agent's skills folder).
name
meeting-minutes
description
Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.

Meeting Minutes Skill — Short Internal Meetings

Purpose / Overview

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.

When to Use

Use this skill when:

  • Internal syncs, standups, design reviews, triage, planning or ad-hoc meetings with short duration
  • Situations that require a concise record of decisions, assigned action items, and follow-ups
  • Creating a standardized minutes document from a live meeting, transcript, recording, or notes

Operational Workflow

Phase 1: Intake (before drafting)
  • Obtain meeting metadata: title, date, start/end time (or duration), organizer, and intended audience.
  • Confirm available inputs: agenda, slides, recording, transcript, or raw notes.
  • If key details are missing, ask up to 3 clarifying questions before producing minutes (see "Discovery" below).
Phase 2: Capture (during / immediately after meeting)
  • Record attendees and absentees.
  • Capture brief notes per agenda item with time markers if available.
  • Record explicit decisions, rationale summary (1–2 sentences), and action items (owner + due date).
Phase 3: Drafting
  • Generate minutes following the Strict Minutes Schema (below).
  • Ensure every action item includes owner, due date (or timeframe), and acceptance criteria when applicable.
  • Mark unresolved issues or items requiring follow-up in the Parking Lot.
Phase 4: Review & Publish
  • If possible, send draft to meeting organizer or a designated reviewer for quick verification (within 24 hours).
  • Publish final minutes to the agreed channel (shared drive, repo, ticket, or email) and optionally create tasks in the team's tracker.

Discovery (required clarifying questions)

Before generating minutes, the agent MUST ask up to three clarifying questions if any of these are missing:

  • What is the meeting title, date, start time (or duration), and organizer?
  • Is there an agenda or transcript/recording to reference? If yes, please provide.
  • Who should be assigned as the reviewer or approver for the minutes?

If the user responds "no transcript" or "no agenda," proceed but mark source material as "ad-hoc notes" and flag potential gaps.

Strict Minutes Schema (Output Structure)

You MUST produce meeting minutes following this exact structure. If information is unavailable, use TBD or Unknown and explain how to obtain it.

1. Metadata
  • Title:
  • Date (YYYY-MM-DD):
  • Start Time (UTC):
  • End Time (UTC) or Duration:
  • Organizer:
  • Location / Virtual Link:
  • Minutes Author (agent or person):
  • Distribution List (who receives the minutes):
2. Attendance
  • Present: [list of names + roles]
  • Regrets / Absent: [list]
  • Notetaker / Recorder: [name or "agent"]
3. Agenda

Bullet list of agenda items, in order:

  • Item 1: short title
  • Item 2: short title
  • ...
4. Summary

A concise one-paragraph summary (1–3 sentences) of the meeting's objective and high-level outcome.

5. Decisions Made

Each as a separate bullet:

  • Decision 1: statement of decision.
    • Who decided / approved: [name(s) or group]
    • Rationale (1–2 sentences): brief reason.
    • Effective date (if applicable): YYYY-MM-DD
  • Decision 2: ...
6. Action Items

Table-style bullets; must include owner and due date:

  • [ID] Action: short description
    • Owner: Name (team)
    • Due: YYYY-MM-DD or "ASAP" / timeframe
    • Acceptance Criteria: (what completes this action)
    • Linked artifacts / tickets: (optional URL or ticket id)

Example:

  • [A1] Draft deployment runbook for feature X
7. Notes by Agenda Item

Brief, factual, timestamp optional:

  • Agenda Item 1: title
    • Key points:
      • Point A (timestamp 00:05)
      • Point B (timestamp 00:12)
    • Open issues / questions:
      • Q1: question text (owner if assigned)
  • Agenda Item 2: ...
8. Parking Lot / Unresolved Items
  • Item: short description
    • Why parked / next step:
    • Suggested owner or next meeting to resolve
Show full SKILL.md (399 more words)Show less
9. Risks / Blockers (if any)
  • Risk 1: short description, impact, mitigation owner
  • Risk 2: ...
10. Next Meeting / Follow-up
  • Proposed date/time (if any)
  • Objectives for next meeting
11. Attachments / References
  • Agenda document: URL
  • Slides: URL
  • Transcript / Recording: URL
  • Related tickets: list of URLs or IDs
12. Version & Change Log
  • Version: 1.0
  • Last updated: YYYY-MM-DDTHH:MM:SSZ
  • Changes: short notes on edits and who made them

Style & Quality Rules

  • Keep minutes concise: total length should typically be under 1 A4 page for meetings <= 30 minutes and under 2 pages for meetings close to 60 minutes.
  • Use plain language and bullet lists for readability.
  • Prioritize decisions and action items at the top of the document.
  • Do NOT include speculative language or unverified claims. If something is uncertain, label it TBD and note the missing info source.
  • Use consistent timestamps and ISO 8601 dates (YYYY-MM-DD or full UTC timestamp).

DO / DON'T

DO:

  • Include owner and due date for every action item.
  • Provide acceptance criteria for action items when possible.
  • Link to artifacts (tickets, slides, recordings) for traceability.
  • Send draft for quick review if minutes contain significant decisions.

DON'T:

  • Omit decisions or action items — these are the primary value of minutes.
  • Mix personal opinions with facts. Keep commentary clearly marked as "Opinion" or exclude it.
  • Publish raw PII gathered during discussion unless required and authorized.

Example Prompts (for Copilot / Agent)

Prompt to generate minutes from transcript:

"Generate meeting minutes from the following meeting transcript. Meeting title: 'Platform Weekly Sync'. Date: 2026-02-10. Duration: 45 minutes. Organizer: Priya (Platform Lead). Transcript: <paste transcript>. Follow the Strict Minutes Schema. Highlight decisions and create action items with owners and due dates where implied."

Prompt to generate minutes from notes:

"I have raw notes from a 30-minute design review. Title: 'Feature Y Design Review'. Date: 2026-02-11. Notes: <paste notes>. Produce concise minutes following the Strict Minutes Schema. Ask up to 3 clarifying questions if critical fields are missing."

Quick Templates (copyable)

Concise minutes template (short):
- Title:
- Date:
- Organizer:
- Present:
- Summary:
- Decisions:
  - Decision 1 — Who — Effective:
- Action Items:
  - [A1] Action — Owner — Due — Acceptance Criteria
- Next Steps / Next Meeting:
Detailed minutes template (full schema):

Use the Strict Minutes Schema above.

Verification & Acceptance Criteria for Generated Minutes

A generated minutes document is acceptable if:

  • It contains Metadata, Attendance, Decisions, and Action Items sections.
  • Every action item has an assigned owner and a due date or a clear timeframe.
  • All significant decisions are captured with at least 1-line rationale.
  • Attachments or references are listed or explicitly marked None.
  • The document is factual; uncertain items are labeled TBD.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/meeting-minutes of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Meeting Minutes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Meeting Minutes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Meeting Minutes this skillgithub/awesome-copilot40k2 repos~2kAutomated safety check: PassMIT
Ingestcoreyhaines31/makerskills844—~1.8kAutomated safety check: PassMIT
Qv Daily Work Updatetetherto/qvac674—~1kAutomated safety check: PassApache-2.0
Standuphaacked/dotfiles134—~3.2kAutomated safety check: PassNone
Qv Devops Daily Updatetetherto/qvac674—~3kAutomated safety check: PassApache-2.0
Kill The StandupVarnan-Tech/opendirectory672—~1.3kAutomated safety check: NotesMIT

Similar skills

  • Ingest

    coreyhaines31/makerskills

    When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into…

    844 GitHub stars~1.8k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

  • Qv Daily Work Update

    tetherto/qvac

    Generate a concise end-of-day work update from local diary, GitHub activity, PR queue state, and optional Asana config.

    674 GitHub stars~1k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Standup

    haacked/dotfiles

    Generate standup notes from GitHub PR activity. An agent skill from haacked/dotfiles.

    134 GitHub stars~3.2k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

  • Qv Devops Daily Update

    tetherto/qvac

    Compose a daily standup in the team's Slack format (🔨 Done today / 📅 Planned for tomorrow / 🚧 Blockers / risks), aggregating recent PRs, reviews, and CI from tetherto/qvac.

    674 GitHub stars~3k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Kill The Standup

    Varnan-Tech/opendirectory

    Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack.

    672 GitHub stars~1.3k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check: notes

  • Issue From Notes

    AxonIQ/AxonFramework

    Create well-structured GitHub issues from any source: meeting notes, transcriptions, conversation context, informal descriptions, or direct requests.

    3.6k GitHub stars~1.1k tokensUpdated today
    Productivity & AutomationAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Meeting Minutes

What does Meeting Minutes do?

Generate concise, actionable meeting minutes for internal meetings. Meeting Minutes is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Generate concise, actionable meeting minutes for internal meetings.

When should I use Meeting Minutes?

Meeting Minutes fits situations like: tasks that involve Meeting notes and agendas.

How do I install Meeting Minutes in Claude Code?

Run `npx skills add github/awesome-copilot --skill meeting-minutes -a claude-code`. Or copy the skill folder (skills/meeting-minutes in github/awesome-copilot) into .claude/skills/meeting-minutes in your project. Claude Code loads it when a task matches its description.

How do I install Meeting Minutes in Codex?

Run `npx skills add github/awesome-copilot --skill meeting-minutes -a codex`. Or copy the skill folder (skills/meeting-minutes in github/awesome-copilot) into .agents/skills/meeting-minutes in your project. Codex loads it when a task matches its description.

Can I use Meeting Minutes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill meeting-minutes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meeting-minutes, .gemini/skills/meeting-minutes, .github/skills/meeting-minutes and .opencode/skills/meeting-minutes in your project.

What does Meeting Minutes need to run?

SKILL.md names no scripts, command-line tools or credentials: Meeting Minutes is instructions for the agent only.

Does Meeting Minutes access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Meeting Minutes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Meeting Minutes use?

Meeting Minutes is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Meeting Minutes use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Meeting Minutes?

Skills that share tags, products or a category with Meeting Minutes: Ingest (coreyhaines31/makerskills, 844 stars), Qv Daily Work Update (tetherto/qvac, 674 stars), Standup (haacked/dotfiles, 134 stars) and Qv Devops Daily Update (tetherto/qvac, 674 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Meeting Minutes?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.