agentleFS
alectivismalectivism/maven-template/.claude/skills/meeting-followup/SKILL.md

meeting-followup

Skill1 starsChanged 6 months agoMITView on GitHub

Segmented follow-up emails after meetings. Use for "meeting follow-up" or when a transcript/notes are provided.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meeting-prep.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    meeting-prep

    Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only attribute insights/wins to people who actually said them

    line 50
  2. Distinctive:

    Don't include things only MMA staff mentioned in "what members shared" sections

    line 51
  3. Distinctive:

    When quoting, verify the attribution against the transcript

    line 52

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting Follow-Up Email Generator

Process

Step 1: Gather Inputs

Collect or ask for:

  • Meeting transcript, notes, or summary
  • Attendee list with roles (if available)
  • Any poll results or survey data
  • Action items assigned during the meeting

Step 2: Analyze & Segment

Identify distinct recipient groups that need different messages:

Common MMA segments:

  • Attendees — thank + recap + action items
  • No-shows / Regrets — recap + what they missed + next steps
  • Speakers / Presenters — thank + feedback + next opportunity
  • Internal team — debrief + action items + follow-up ownership
  • New contacts — welcome + context + how to get involved

Step 3: Extract Key Content

From the transcript/notes, pull:

  • Decisions made
  • Action items (with owners and deadlines)
  • Key insights or findings shared
  • Questions raised (answered and unanswered)
  • Next meeting date/agenda items

Step 4: Draft Segmented Emails

For each segment, draft an email following MMA style:

  • Subject: [Meeting Name] — [Key Takeaway or Action]
  • Opening: 1 sentence purpose (not "Thank you for attending...")
  • Body: Key points as bullets, action items bolded
  • Close: Next steps with dates
  • Tone: Direct, warm, action-oriented

Step 5: Create Recipient Lists

For each email variant, provide:

  • Recipient list (names and emails if available)
  • Suggested send timing
  • Any personalization needed per recipient

Attribution Rules

  • Only attribute insights/wins to people who actually said them
  • Don't include things only MMA staff mentioned in "what members shared" sections
  • When quoting, verify the attribution against the transcript

Output Format

Present as separate email drafts with recipient lists:

Email 1: [Segment Name]

To: [list] Subject: [subject] Body: [formatted email]

Email 2: [Segment Name]

...

Confirmation

Always present all drafts for review before any sending action.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.