meeting-follow-up
Skill8 starsChanged 5 months agoMITView on GitHub
Converts meeting notes, minutes, or call transcripts into decisions, action items with owners and deadlines, open questions, and a sendable recap. Use when the user shares meeting notes or a transcript, or asks for a meeting summary, recap, minutes, follow-ups, or takeaways.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- jsath/claude-skillstheir own version, first seen Oct 13, 2026
- QuixiAI/Hexistheir own version, first seen Oct 8, 2026
- QuixiAI/agi-memorytheir own version, first seen Oct 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- jsath/claude-skills★ 14same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- answerSkill
- api-to-exampleSkill
- bilingual-readerSkill
- calendar-prepSkill
- caption-assistantSkill
- chart-explainerSkill
- code-translatorSkill
- competitor-snapshotSkill
- coupon-hunterSkill
- course-fit-checkSkill
- cover-letter-builderSkill
- deal-checkerSkill
- draft-from-notesSkill
- explainSkill
- fact-checkSkill
- fix-grammarSkill
- hook-generatorSkill
- improve-writingSkill
- interview-prepSkill
- job-application-assistantSkill
- job-fit-reviewSkill
- job-offer-compareSkill
- landing-page-critiqueSkill
- linkedin-outreachSkill
- localize-textSkill
- outline-builderSkill
- paper-readerSkill
- portfolio-project-reviewSkill
- product-review-summarizerSkill
- pronunciation-and-usageSkill
- regex-decoderSkill
- reply-assistantSkill
- repo-onboarderSkill
- rewrite-longerSkill
- rewrite-shorterSkill
- social-post-generatorSkill
- source-finderSkill
- source-listSkill
- study-planSkill
- style-matchSkill
- summarizeSkill
- table-to-csvSkill
- term-explainerSkill
- terminology-keeperSkill
- tone-rewriterSkill
- translateSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Keep explicit commitments verbatim.
- Distinctive: line 19
If owners or due dates are missing or ambiguous, flag them so the user can confirm before sending.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Meeting Follow-Up
Turn the user's meeting notes or transcript into decisions, action items, open questions, and a sendable recap. Preserve names, numbers, dates, and commitments exactly as stated. Never invent owners or deadlines.
- Extract decisions, action items, owners, deadlines, dependencies, and unresolved questions from the source.
- Keep explicit commitments verbatim. Mark any owner or date you inferred as
(inferred)rather than asserting it. - Group action items by owner or workstream when that makes the recap easier to scan.
- If owners or due dates are missing or ambiguous, flag them so the user can confirm before sending.
- Draft a sendable follow-up message that matches the tone of the source and the user's audience.
Return these sections, omitting any that do not apply: Decisions, Action items (one per line as owner — task — due date), Open questions, Suggested follow-up message. Respond in the same language as the user's notes.
Example
Notes:
standup 6/24 — Priya, Marcus, me agreed to ship the export feature behind a flag Marcus takes the API endpoint, due Friday need to decide pricing tier still — ask Dana someone should update the docs
Output:
Decisions
- Ship the export feature behind a feature flag.
Action items
- Marcus — build the export API endpoint — Fri Jun 26
- You (inferred) — update the docs — no due date set
Open questions
- Which pricing tier does export belong to? (ask Dana)
Suggested follow-up message
Hi team — quick recap of today's standup. We're shipping export behind a flag. Marcus owns the API endpoint, targeting Friday. I'll take the docs update. Still open: which pricing tier export lands in — Dana, can you weigh in?
Owner for the docs update isn't explicit in the notes — confirm before sending.
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
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.