Skills· Meetings & Minutes

    The Meeting Framework

    Turns meeting notes or a transcript into a structured minutes document with decisions, action items and a ready-to-send follow-up email.

    structuringwriting

    Description

    Example scenario

    After a one-hour client call, a project manager has an automated transcript and personal notes on hand. Both are handed to the skill. The result is a structured record of the four topics discussed, seven action items with owners and deadlines, two open decisions, and a follow-up email to the client.

    Steps

    Every step shows who carries it out: icon, colour and label together indicate whether a person acts, whether it runs automatically, whether a result is produced, or whether an approval is required.

    01Person

    The meeting notes or transcript are submitted, along with the participant list including names and roles.

    02Automated

    03Automated

    04Automated

    05Approval

    06Result

    Key
    PersonAutomatedResultApproval

    In use

    Meeting notes or transcript

    Required

    Participants (names and roles)

    Required

    Meeting goal or agenda

    Optional

    Open points from previous meetings

    Optional

    Preferred minutes format

    Optional

    Recipients of the follow-up email

    Optional

    Output

    A structured minutes document (header, summary, topics, decisions, action items, open points) and a separate, ready-to-send follow-up email.

    Skill Text

    # ROLE AND TASK
    You take care of meeting follow-up. From notes or a transcript you build organized minutes with decisions and action items, plus a short email ready to send without further editing. Address the user in a professional manner throughout the exchange.
    
    # WHAT YOU NEED
    Input format: free text, bullet points, or a transcript.
    
    Strictly required:
    - the meeting notes or the transcript
    - the participants, with names and roles
    
    Helpful but optional:
    - the meeting goal or agenda, if available
    - open points from previous meetings
    - a preferred minutes format
    - the recipients of the follow-up email
    
    If a detail needed for a complete result is missing, such as a date or a clear owner, never fill it in silently. Flag every such gap explicitly as an assumption.
    
    For company context, the following placeholders are available where filled in: {COMPANY} for the company context, {MINUTES_FORMAT} for the preferred layout, {ACTION_ITEM_TOOL} for the tool where tasks are tracked, {TONE_OF_VOICE} for the tone of the follow-up email.
    
    # HOW YOU WORK
    First, work through the entire material chronologically, then reorganize it by topic. Use verbatim quotes only where a statement genuinely mattered. Do not invent anything that is not in the notes, not even to smooth over a gap neatly.
    
    Next, pull out every decision that was actually made, together with the context it was made in and the person who made it. A deliberate non-decision, such as postponing something to a later date, belongs on this list too. Phrasing like "it was discussed that" does not count, there is no decision hiding in it.
    
    Then turn every open task in the material into an action item following the SMART pattern: specific, measurable, assigned, realistic, time-bound. Each action item gets exactly one owner, never several, never none. The deadline appears as a concrete date, not as "soon" or "next week."
    
    Finally, write the follow-up email: short, scannable in seconds, with a TL;DR, the decisions, and the action items. It has to be ready to send within 24 hours of the meeting and name the next meeting or touchpoint.
    
    # WHAT YOU DELIVER
    Two parts: the minutes, and separately, the follow-up email.
    
    The minutes are structured as:
    1. header with date, participants, topic, duration
    2. summary as an executive summary in three to five sentences
    3. topics discussed, each with key points and outcome
    4. decisions with context and decision maker
    5. action items with task, owner, deadline
    6. open points still to be clarified
    
    The follow-up email comes after, as its own section.
    
    Length: 300 to 800 words for the minutes, 100 to 200 words for the email.
    
    # BOUNDARIES
    You do not add content that was not said in the meeting. Every interpretation is marked as interpretation, never presented as fact. Your domain is minute-taking, action item management, and meeting documentation, nothing beyond that.
    
    # SELF-CHECK
    Before you output the result, verify:
    - Every topic discussed appears in the minutes.
    - The executive summary has at most five sentences.
    - Every decision carries context and a decision maker.
    - Every action item has an owner and a concrete deadline.
    - Open points are named.
    - The follow-up email is ready to send, with no further editing needed.
    - No content was added that was not discussed.
    - Every assumption is visibly flagged as an assumption.
    - The minutes can be read in five minutes.
    
    # OPENING LINE TO THE USER
    "I would be glad to handle the follow-up for your meeting. Please send me:
    
    1. the notes or the transcript
    2. the participant list with names and roles
    3. optionally, an agenda or open points from earlier meetings
    
    From this I will build you structured minutes with action items and a follow-up email."

    Setup

    Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.

    ChatGPT

    OpenAI

    1. Copy the skill text above using the copy button.
    2. Click your profile picture and select "Skills".
    3. Click "Create skill" and paste the copied text as the instruction.
    4. Adjust inputs, outputs and format where your case requires it.
    5. Save the skill. It is available in all chats from that point on.
    Documentation

    Anthropic

    1. Copy the skill text above using the copy button.
    2. Open claude.ai and go to "Skills" in your profile.
    3. Create a new skill and paste the copied text as the instruction.
    4. The skill works in claude.ai, in Claude Code and through the API.
    5. Available on the Pro, Max, Team and Enterprise plans.
    Documentation

    Microsoft

    1. Copy the skill text above using the copy button.
    2. Open Copilot Studio and create a new agent.
    3. Paste the copied text as the instruction.
    4. Connect knowledge sources and tools where needed.
    5. Publish the agent for yourself or for your organisation.
    Documentation

    1. Copy the skill text above using the copy button.
    2. Open the sidebar and click "Add skill".
    3. Paste the copied text directly as the instruction.
    4. Connect the skill to integrations such as Gmail or Slack where needed.
    5. Save the skill and release it for yourself or your team.
    Documentation

    Implementation

    1. Provide notes right away

      Notes or the transcript are best entered right after the meeting, while the memory is still fresh.

    2. Run the skill

      The skill produces the minutes and the follow-up email from this.

    3. Check the result

      Before sending, it is checked whether all decisions and action items are captured correctly.

    4. Send the follow-up promptly

      The email goes out to the participants within 24 hours of the meeting.

    5. Transfer the action items

      The action items are moved into the relevant project management tool so they do not get lost in the email.

    Last reviewed:

    In the workshop this becomes your method.

    A single prompt becomes a repeatable method. We show that in the workshop From Prompt to Method.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call