Meeting notes to actions

pacpio-team/meeting-notes-to-actions
Copy project link
Public
Anyone can see and download this project, even without signing in.
Owner: Pacpio Team Made by the Pacpio team
Made by the Pacpio team
Report

Use it with your AI

Works in Claude, ChatGPT or any other AI

  1. Step 1: Connect your AI

    Do it once. It takes a minute.

    Connect your AI

  2. Step 2: Ask your AI

    Paste this into your chat:

    What does the Pacpio project pacpio-team/meeting-notes-to-actions do?

Make a copy Sign in to get your own project to change. Download a copy All files in one ZIP. The copy doesn’t update by itself.

SKILL.md

1.4 KB · 26 lines
Copy the text
Download this file
name description
follow-up-message Writes the short message to participants after a meeting, decisions and each person's action items with dates; use for "send the summary".

Follow-up message

Use when: the record is done and the user wants to tell the participants what was decided and who does what.

Input

The meeting record (the latest in meetings/, or the one named). The channel: email or messenger. Whether the participants are the team or outside people.

Steps

  1. Read the record and my/team.md.
  2. Write up to 150 words: one line of thanks; the decisions as a short list; the action items grouped by person, each with its date; the next meeting; one line on how to raise corrections.
  3. Tone: plain for the team; a little more formal for outside participants. No "as discussed", no "per my last message".
  4. Save the message in the record under "Follow-up" (note "Follow-up message added").
  5. Answer with the message, ready to paste.

Output

The message, in the record's language unless the user asks for another.

Edge cases

  • The user wants only their own items sent to one person: a two-line message to that person; save it under "Follow-up" too, with the recipient's name.
  • Items without an owner: list them under "Still unassigned" and ask the group who takes them.
  • The record has "unclear, confirm" marks: put them in the message as questions, not as facts.
---name: follow-up-messagedescription: Writes the short message to participants after a meeting, decisions and each person's action items with dates; use for "send the summary".---# Follow-up messageUse when: the record is done and the user wants to tell the participants what was decided and who does what.## InputThe meeting record (the latest in `meetings/`, or the one named). The channel: email or messenger. Whether the participants are the team or outside people.## Steps1. Read the record and `my/team.md`.2. Write up to 150 words: one line of thanks; the decisions as a short list; the action items grouped by person, each with its date; the next meeting; one line on how to raise corrections.3. Tone: plain for the team; a little more formal for outside participants. No "as discussed", no "per my last message".4. Save the message in the record under "Follow-up" (note "Follow-up message added").5. Answer with the message, ready to paste.## OutputThe message, in the record's language unless the user asks for another.## Edge cases- The user wants only their own items sent to one person: a two-line message to that person; save it under "Follow-up" too, with the recipient's name.- Items without an owner: list them under "Still unassigned" and ask the group who takes them.- The record has "unclear, confirm" marks: put them in the message as questions, not as facts.