ThinkFacility

Skills · Work

Turn my meeting notes into a memo

Paste the mess you typed during the call. Get something you can send.

SKILL.md

meeting-memoThe whole skill. Nothing else to fill in.
---
name: meeting-memo
description: Turn raw meeting notes into a short memo with decisions, owners and open questions. Use whenever the user pastes meeting notes, standup notes, call notes or a transcript and wants it written up.
---

# Meeting notes to memo

Turn messy notes into a memo somebody will actually read.

## Steps

1. Read the notes and work out what was decided, what was only discussed, and what is still open. These are different things and most notes blur them.
2. Write the memo in this order, and skip any section that would be empty:

   **Decisions.** One line each, in the past tense, naming who decided if the notes say.
   **Owners.** Who is doing what by when. If a date was not given, write "no date given" rather than inventing one.
   **Open questions.** The things nobody settled.
   **Context.** Only if a reader who missed the meeting would be lost without it. Two sentences at most.

3. Keep the whole memo under 200 words unless the notes genuinely carry more.

## Rules

- Never invent an owner, a date or a decision. If the notes are ambiguous, put the item under Open questions and say what is unclear.
- Strip the chat: greetings, tangents, and who said hello.
- Use the words the meeting used. If they said "the Preston job", do not translate it to "the client engagement".
- If the notes contain something that reads as sensitive, for example someone's performance or pay, leave it out of the memo and tell the user you did.

## Output

Plain markdown, ready to paste into email or Slack. No preamble, no "here is your memo". Start at the first heading.

Where it goes

Claude Code: save the file as ~/.claude/skills/meeting-memo/SKILL.md. The folder name has to match, and a new session picks it up.

claude.ai: turn on code execution in Settings → Capabilities, then go to Customize → Skills and upload the zip. The zip already has the folder at its root, which is what that upload wants.

When it fires

Claude decides by reading one line, the description at the top of the file. This one says: Turn raw meeting notes into a short memo with decisions, owners and open questions. Use whenever the user pastes meeting notes, standup notes, call notes or a transcript and wants it written up.

Why the description matters more than the skill

Claude decides whether to use a skill by reading its description and nothing else. That is why this one lists the words people actually type, like "write this up", rather than describing the skill in the abstract. A description that says "a professional memo generation utility" almost never fires.

The instruction that does the work

Separating decisions from discussion. Notes blur them constantly, and a memo that presents a passing idea as a decision causes real problems. Everything ambiguous is pushed into Open questions instead of guessed at.

Install one of these next