Automated summary
Turns raw meeting notes, whether pasted or read from files, into polished minutes following a fixed Markdown template.
Strengths
- Strict, repeatable output template covering attendees, discussion, actions, and next meeting
- Collects every action item into one table with owner and status
- Reads and merges multiple sources (.eml, .txt, .md, .docx) before organizing
- Uses [TBD]/[Unknown] placeholders instead of inventing names, dates, or decisions
Limitations
- The template is fixed, so no extra sections or alternative minutes formats
- No automatic timestamps of exchanges and no condensed executive summary
- Writes a file only when the user explicitly asks for it
Use it right after a meeting when raw notes need to become clean, shareable minutes.
Skip it when you want analytical synthesis or creative rewriting rather than factual minutes that follow the template.
Security analysis
SafeThe skill declares only Read, Write, and AskUserQuestion — no bash, network, or destructive operations. Its instructions are limited to reading user-specified note files (including .eml body extraction) and rendering Markdown minutes in chat, with file saving only on explicit user request. No secrets are exfiltrated, no obfuscated payloads, no safety bypasses; the toolset is proportionate to the task.
No concerns found
How this analysis is madeExamples
meeting-minutes Voici mes notes brutes du comité produit de ce matin, mets-les en forme en compte rendu : on a parlé du retard de la v3, Léa relance le prestataire avant vendredi, budget à revoir en septembre.../meeting-minutes ./inbox/2024-06-12-kickoff.eml ./inbox/2024-06-12-followup.txt — fusionne ces deux sources et produis les minutes de la réunion de lancement.meeting-minutes Génère les minutes à partir de ces notes puis enregistre-les dans docs/minutes/2024-06-12-sprint-review.mdname: meeting-minutes description: Converts raw, unorganized meeting notes into polished meeting minutes using a structured Markdown template. argument-hint: <notes-or-file-path> allowed-tools: Read, Write, AskUserQuestion
You are converting raw, unorganized meeting notes into polished meeting minutes.
Instructions
Step 1 — Gather input
Ask the user for their source material. They may provide any combination of:
- Pasted text — raw notes typed or copied directly into chat
- File paths — one or more paths to files on disk (e.g.
.eml,.txt,.md,.docx)
If file paths are provided, read each file using your file reading tools before proceeding. For .eml files, extract only the plain-text body and ignore HTML, headers, and MIME metadata. If multiple sources are provided, merge them into a single pool of information before organizing.
Step 2 — Extract and organize
- Read all source material carefully and extract all meaningful information.
- Organize the output using exactly the template structure below.
- For any field you cannot find in the source material, use
[TBD]or[Unknown]as a placeholder — do not guess or invent names, dates, or decisions. - Group scattered discussion points into logical topics. Infer topic headings from context if none are explicitly stated.
- Consolidate all action items into a single table at the end. Do not duplicate them under Discussion topics.
- Each Discussion topic must end with a
> **Next Step:**line. If none is clear from the notes, write> **Next Step:** [TBD]. - Display the formatted minutes in chat. Do not save to a file unless the user asks.
Output Format
Use this structure exactly. Do not add or remove sections.
# [Meeting Title]
**Date/Time:** [MM/DD/YYYY] | [HH:MM AM/PM]
**Location/Call:** [Room name or Teams/Zoom link]
**Facilitator:** [Name]
**Note-taker:** [Name]
**Purpose:** [One sentence describing the objective of this meeting]
---
## Attendees
- [Name, Title]
- [Name, Title]
---
## Discussion
### [Topic Name]
- [Discussion point]
- [Discussion point]
> **Next Step:** [Who does what by when]
---
### [Topic Name]
- [Discussion point]
- [Discussion point]
> **Next Step:** [Who does what by when]
---
## Action Items
| # | Action | Owner | Status |
|---|--------|-------|--------|
| 1 | | | Pending |
---
## Next Meeting
**Date/Time:** [MM/DD/YYYY] | [HH:MM AM/PM]
**Anticipated Topics:**
- [Topic]
Rules
- Preserve the meaning of every note — do not drop details or silently rephrase decisions.
- Write discussion points as complete, clear sentences (not fragments).
- Action items must name a specific owner. If no owner is stated, use
[Unknown]. - Do not add commentary, summaries, or editorial opinions outside the template structure.
- After displaying the output, ask: "Would you like to save this to a file?"
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/meeting-minutes-mrzxuqnk/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/meeting-minutes-mrzxuqnk' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/meeting-minutes-mrzxuqnk/download' --output '.skill-downloads/meeting-minutes-mrzxuqnk/SKILL.md.part' && mv '.skill-downloads/meeting-minutes-mrzxuqnk/SKILL.md.part' '.skill-downloads/meeting-minutes-mrzxuqnk/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, AskUserQuestion
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/meeting-minutes-mrzxuqnk/SKILL.md' && test -s '.skill-downloads/meeting-minutes-mrzxuqnk/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/meeting-minutes' && cp -R '.skill-downloads/meeting-minutes-mrzxuqnk' '.claude/skills/meeting-minutes'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/meeting-minutes-mrzxuqnk'openskills read 'meeting-minutes-mrzxuqnk'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/meeting-minutes-mrzxuqnk/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
PDF Reader
Productivity
Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.
Discord Messaging Workflows
Productivity
Use the message tool to send, edit, and moderate Discord messages with interactive components.
Interactive Verdict Preview
Productivity
Generate an interactive HTML preview of keep/drop verdicts for maintainer review, then process the pasted feedback JSON.