zheng
dd8e0f55c3
Improve first-run and channel setup for non-technical users: detect newer Gemini key formats, pin Node 22.22.3, add Control Panel Telegram approve flow, and keep channels/models when config is rewritten. Persist uclaw wizard state via uclaw-meta.json so restarts skip language/persona prompts. Co-authored-by: Cursor <cursoragent@cursor.com>
73 lines
2.1 KiB
Markdown
73 lines
2.1 KiB
Markdown
---
|
|
name: meeting-notes
|
|
description: "Meeting notes - turn a rough transcript or scribbles into notes with decisions, owners and dates"
|
|
metadata: { "openclaw": { "emoji": "🗒️" } }
|
|
---
|
|
|
|
# Meeting Notes
|
|
|
|
Turn whatever you captured — a transcript, half-typed bullets, a voice memo
|
|
transcription — into something you can send within a few minutes of the meeting.
|
|
|
|
## The shape
|
|
|
|
```
|
|
Subject · date · who was there
|
|
|
|
Decisions
|
|
- What was decided, and by whom if it matters
|
|
|
|
Actions
|
|
- [Owner] What, by when
|
|
|
|
Discussed, not decided
|
|
- Points raised that need another conversation
|
|
|
|
Open questions
|
|
- What nobody in the room could answer
|
|
```
|
|
|
|
**Decisions and actions come first** because they are the only parts anyone reads
|
|
twice. A chronological retelling of the conversation is not notes.
|
|
|
|
## Rules that matter
|
|
|
|
- **Every action needs a name and a date.** "We should follow up" is not an
|
|
action. If the meeting never assigned one, write `[unassigned]` — visibly
|
|
missing beats quietly dropped.
|
|
- **Do not invent decisions.** If a discussion trailed off, it goes under
|
|
"discussed, not decided". Notes that record a decision nobody made cause real
|
|
arguments later.
|
|
- **Quote figures and dates exactly.** If the transcript is ambiguous about a
|
|
number, flag it rather than guessing.
|
|
- **Keep names as spoken.** Do not promote "Wei" to "Mr Wei Ming Tan" unless the
|
|
meeting used it.
|
|
|
|
## Example prompts
|
|
|
|
```
|
|
Turn this transcript into notes I can send to the client
|
|
```
|
|
|
|
```
|
|
Pull just the action items out, grouped by who owns them
|
|
```
|
|
|
|
```
|
|
Write the follow-up email — thank them, confirm the two decisions, ask about the
|
|
pricing question that was left open
|
|
```
|
|
|
|
## After the meeting
|
|
|
|
The usual next step is an email. Keep it short: what was decided, what you owe
|
|
them, what you need from them, by when. The full notes go underneath or attached.
|
|
|
|
## Working notes
|
|
|
|
- Dates in Singapore format, DD/MM/YYYY, and say the day of the week for
|
|
anything within the next fortnight — "by 22/08 (Friday)" removes a whole class
|
|
of misunderstanding.
|
|
- If the recording is partial, say which parts are missing rather than smoothing
|
|
over the gap.
|