Stats
Actions
Tags
From distillery
Captures structured meeting notes, stores them in the Distillery knowledge base, and supports appending updates or listing recent meetings via /minutes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/distillery:minutesThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- Trigger phrases: minutes, meeting notes, capture meeting, log meeting, /minutes, /minutes --update <meeting_id>, /minutes --list -->
Minutes captures structured meeting notes, stores them in the Distillery knowledge base, and supports appending updates or listing recent meetings.
/minutes)/minutes --update <meeting_id>)/minutes --list)See CONVENTIONS.md — skip if already confirmed this conversation.
--update <meeting_id> → Update Mode--list → List ModeOptional flags (all modes):
| Flag | Parameter | Description |
|---|---|---|
--project | <name> | Filter by project name (used in List Mode to scope results) |
Collect from the user (or extract from invocation context): title/topic, attendees, key discussion points, decisions, action items (with owners), and optional follow-ups. Require at least a title and one discussion point, decision, or action item.
Format: <slugified-title>-<YYYY-MM-DD> — lowercase, replace non-alphanumeric with hyphens, collapse multiples.
Examples: "Architecture Review" on 2026-03-22 → arch-review-2026-03-22, "Daily Standup" → daily-standup-2026-03-22
Compose structured notes:
# Meeting: <Title>
**Date:** <YYYY-MM-DD>
**Attendees:** <comma-separated list>
**Meeting ID:** <meeting_id>
## Discussion
<bullet list or short paragraphs>
## Decisions
<bullet list>
## Action Items
<bullet list with owners/deadlines>
## Follow-ups
<if any — omit section if empty>
Show preview and ask: Ready to store? (yes / edit / skip). If skip: "Skipped. No meeting entry was stored."
Determine author & project per CONVENTIONS.md. Auto-extract 2-5 lowercase, hyphen-separated tags from the content.
First, check for an existing meeting with the same meeting_id:
distillery_search(query="<meeting_id>", entry_type="minutes", limit=5)
If any result has metadata.meeting_id == <meeting_id>, treat this as a duplicate meeting record. Display:
A meeting entry with ID "<meeting_id>" already exists (entry <entry-id>).
Use /minutes --update <meeting_id> to append new content instead.
Proceed anyway? (yes / skip)
If user chooses skip: "Skipped. No new entry was stored." and stop.
If no meeting_id match found, call distillery_find_similar(content="<meeting notes summary>", dedup_action=True). Handle by action field:
"create": No similar entries. Proceed to Step 7a.
"skip": Near-exact duplicate. Show similarity table and offer: (1) Store anyway, (2) Skip.
"merge": Very similar entry exists. Show similarity table and offer: (1) Store anyway, (2) Merge with existing, (3) Skip.
For merge: combine new notes with the most similar entry's content, call distillery_update with the entry ID and merged content, confirm and stop.
"link": Related but distinct. Show similarity table, note new entry will be linked. Ask to proceed or skip. If proceeding, include "related_entries": ["<id1>", ...] in metadata at Step 7a.
Similar entries found:
| Entry ID | Similarity | Preview |
|----------|-----------|---------|
| <id> | <score%> | <content_preview> |
On skip in any case: "Skipped. No new entry was stored." and stop.
distillery_store(
content="<formatted notes>",
entry_type="minutes",
author="<author>",
project="<project>",
tags=[...],
metadata={
"meeting_id": "<meeting_id>",
"attendees": ["<attendee1>", ...],
"version": 1
}
)
[minutes] Stored: <entry-id>
Project: <project> | Author: <author>
Summary: <first 200 chars of notes>...
Tags: tag1, tag2, tag3
distillery_search(query="<meeting_id>", entry_type="minutes", limit=5)
Match on metadata.meeting_id. If no match: offer to create a new meeting instead, or stop with "No changes made." The --update flag requires a meeting_id; if omitted, ask which meeting to update.
Show a brief summary of the existing meeting (title, date, version). Collect new notes, decisions, action item updates, or corrections. Require at least one meaningful addition.
Append under a timestamped heading (never overwrite original):
## Update — <YYYY-MM-DD HH:MM:SS UTC>
<new content>
Show the appended section and ask: Ready to append? (yes / edit / skip)
Set new_version = current_version + 1. Call distillery_update with the full content (original + appended section) and updated metadata including the new version.
[minutes] Stored: <entry-id>
Project: <project> | Author: <author>
Summary: <first 200 chars of update section>...
Tags: tag1, tag2, tag3
distillery_list(entry_type="minutes", limit=10, output_mode="full")
If --project was specified, also pass project=<name> to scope results to that project.
If none found: "No meeting entries found. Use /minutes to capture your first meeting."
Otherwise display a compact table:
Recent Meetings (10 most recent):
| Meeting ID | Title | Date | Attendees |
|------------------------------|----------------------|------------|-----------|
| arch-review-2026-03-22 | Architecture Review | 2026-03-22 | 4 |
Columns: metadata.meeting_id, title from # Meeting: heading, date from content or created_at, count of metadata.attendees.
meeting_id format: <slugified-title>-<YYYY-MM-DD>## Update — <timestamp>; never overwrite original contentversion starts at 1, increments by 1 on each updateentry_type="minutes" for store/list/search callsmetadata.attendees must be a list of strings, not comma-separatednpx claudepluginhub norrietaylor/distillery --plugin distilleryStructures and formats meeting notes using PM best practices with templates for agendas, decisions, action items, discussions, and next steps. Useful for capturing outcomes from meetings like 1:1s or sprint planning.
Structures meeting notes with templates for decisions, action items, and follow-ups following PM best practices.
Captures team discussions, meeting notes, and conversations into structured Markdown files with participants, key points, decisions, action items, and updates monthly YAML indexes.