How do I install the Followup skill?

Run npx skillmds@latest add nord342/followup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Followup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Followup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Followup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Followup?

nord342 (@nord342) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Followup by nord342 — Agent Skill

Name: Followup
Author: nord342

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.

nord342 2855545 2.6 KB Updated Sep 17, 2026

File contents

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?"

---name: followupdescription: 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.---# Draft Follow-upsTurn 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 produceDecide 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.## OutputWrite 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?"*

Frequently asked questions