General bay
Meeting notes
PromptStableby @julian2026-05-27
Copies
—
loading…
Views
—
loading…
Spice
Anyone in the studio. Open and go.
paste into Claude, or drop the file into a Claude Code skills dir
What it does
Takes raw meeting notes and turns them into a structured summary, decisions made, actions with owners, and open questions.
When to use
- After any client meeting or internal session
- When you need to send a follow-up but your notes are messy
- For anything that generated actions that need tracking
The skill
Turn my meeting notes into a structured summary.
Format:
- Meeting: [title, date, attendees, fill from my notes or leave blank if not present]
- In a sentence: What was this meeting about and what came out of it?
- Decisions made: A bullet for each. Specific.
- Actions: Each on its own line, [Owner] · [Action] · [Due date if mentioned]
- Open questions: Things raised but not resolved
- Next meeting: If mentioned
Don't invent decisions or actions that aren't clearly in my notes. If it's ambiguous who owns an action, flag it rather than guessing.
Here are my notes:
[paste notes]
Comments & reactions
Comments arrive once we point Giscus at the repo. Threads in GitHub Discussions. Reactions count as votes. No new logins.