meeting-notes-distiller
SkillDocs & knowledgeTurns raw meeting notes or transcripts into structured decisions and action items. Use after a meeting when raw notes/transcript exist and need to become a shareable summary.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the meeting-notes-distiller skill
What this skill tells your AI
The instructions your AI receives, as published by codebygarv/ai-skills in skills/productivity/meeting-notes-distiller/SKILL.md and read by ahel’s review.
Purpose
Convert raw, unstructured meeting notes or a transcript into a clean summary of what was decided and what needs to happen next — the artifact people actually reread, instead of scrolling back through a wall of raw notes.
When to Use
- A meeting just happened and raw notes/transcript exist that need to become a shareable summary.
- Someone missed a meeting and needs to catch up without reading the full transcript.
- A recurring meeting needs a consistent summary format over time.
What to Analyze / Do
- Separate discussion from decisions — most of a meeting is discussion; only some of it results in an actual decision. Distinguish clearly between "this was debated" and "this was decided."
- Extract action items — each with an owner if stated or clearly implied, and a deadline if one was mentioned; mark "owner unclear" rather than guessing.
- Note open questions — things that were raised but not resolved, so they don't silently disappear.
- Preserve important context/rationale for non-obvious decisions — "we chose X" is less useful than "we chose X because Y consideration outweighed Z," when that reasoning was actually discussed.
- Keep it short — a meeting summary that's nearly as long as the transcript defeats the purpose.
Output Format
- Decisions — bullet list, each a clear, standalone statement.
- Action Items — table: Action | Owner | Deadline (if any).
- Open Questions — bullet list of unresolved items.
- Optional Context section for decisions that need a brief "why," only when genuinely useful.
Avoid
- Padding with a full chronological recap of everything discussed — summarize outcomes, don't transcribe.
- Inventing an owner or deadline that wasn't actually stated or clearly implied.
- Losing genuinely important dissenting opinions or open questions in service of a tidy-looking summary.
Signals
- GitHub stars
- 25
- Forks
- 1
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
meeting-notes-distiller- Source
- github.com/codebygarv/ai-skills