Followup

Skill nord342/claude-meeting-notes/meeting-notes/skills/followup

Draft ready-to-send follow-up messages from a meeting recap — a recap email to all attendees and/or individual notes to each person reminding them of what they own. Use after a meeting when the user wants to send a summary or nudge people on their action items.From its SKILL.md

Install

npx -y skills add nord342/claude-meeting-notes --skill followup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 592 tokens by cl100k_base, as published. Nobody here has run it

Draft Follow-ups

Turn a recap into messages the user can actually send. Default to the most recent recap in ./Meetings/recaps/ unless $ARGUMENTS names a file or a person.

Uses the follow-up structure in ${CLAUDE_PLUGIN_ROOT}/skills/meeting-notes/templates/followup.md and pulls action items from the recap / ACTIONS.md.

What to produce

Decide based on $ARGUMENTS:

No argument → draft a group recap email to all attendees (TL;DR + decisions + everyone's action items) AND offer to generate per-person nudges.
A person's name → draft a personal note to just that person, listing only the items they own, with due dates.
A recap file path → use that meeting instead of the latest.

Drafting rules

Match a normal professional tone — warm, concise, skimmable. Not robotic, not over-formal. Short sentences. No corporate filler.
Open with one line of context ("Thanks all for the product sync today — quick recap and who's doing what:").
Put action items as a checklist with owners and due dates so they're unmissable.
For personal nudges, lead with their items, keep it friendly, and make the ask explicit ("Could you get the pricing deck over by Fri?").
Never invent details, names, or commitments not in the recap.
Leave a clearly-marked placeholder for anything you can't know (e.g. [your name], [link to deck]) rather than guessing.

Output

Write drafts to ./Meetings/recaps/ next to the source recap, as YYYY-MM-DD-<slug>-followup.md (group) and/or ...-followup-<person>.md (personal). Also show each draft inline in chat so the user can copy-paste immediately.

End by reminding the user these are drafts to review and send themselves — this plugin never sends anything, it just writes the message.

Example

User: /meeting-notes:followup Sarah

You: produce a short personal note:

To: Sarah Subject: Quick follow-up from today's product sync

Hi Sarah — thanks for jumping in today. Two things on your plate from the sync:

Send the pricing deck — by Fri Jul 3

Confirm the Q3 launch date with marketing — by Wed Jul 1

Shout if either needs a hand. Thanks! [your name]

Then: "Drafted and saved to Meetings/recaps/2026-06-29-product-sync-followup-sarah.md. Want the group recap email too?"

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.