meeting-followup
Skill0 starsChanged 42 days agoMITView on GitHub
Turn a recorded meeting or call into decisions, owners, deadlines and the message that goes out afterwards. Use when the user asks for minutes, action items, a recap, a follow-up email, or what they committed to on a call.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- jp-solumhealth/jpstacktheir own version, first seen Oct 14, 2026
- runxhq/runxtheir own version, first seen Oct 13, 2026
- cyxar4uk/ya360-mcptheir own version, first seen Sep 27, 2026
- sami2919/SignalForcetheir own version, first seen Aug 4, 2026
- ozzy-labs/opshubtheir own version, first seen Jun 14, 2026
- dshaplyko/skillstheir own version, first seen Jun 4, 2026
Used with
Projects with it also use meeting-prep and research.
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.
OpenAISkillmeeting-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
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- runxhq/runx★ 97same name
- sami2919/SignalForce★ 9same name
- cyxar4uk/ya360-mcp★ 2same name
- dshaplyko/skills★ 2same name
- ozzy-labs/opshub★ 2same name
- alectivism/maven-template★ 1same name
- yakatotech/claude_code_env★ 1same name
- jp-solumhealth/jpstack★ 0same 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 repository3 other files it gives its agents.
- find-the-momentSkill
- interview-notesSkill
- lecture-notesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Check get_transcript_summary first.
- Distinctive: line 14
Write the follow-up in the register of the meeting.
- Distinctive: line 16
Never invent an owner or a deadline that nobody said.
- Distinctive: line 18
If the user wants the message sent, hand them the draft.
“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.
Files
The work after a meeting is always the same: what was decided, who owes what, and the message that goes out.
- Find the meeting. If the user named it, use
list_transcriptsand match on the title and date. If they described it instead,search_transcriptson a phrase that would have been said in it. - Check
get_transcript_summaryfirst. When RiverScript already generated a summary, it saves reading the whole thing. When it returns nothing, that is normal: fetch the text withget_transcript. - Pull out, in this order, and only what the transcript actually supports:
- decisions, each with the reasoning if it was given
- actions, each with an owner and a date when one was named, and plainly marked as unassigned when not
- open questions that were raised and left unanswered
- Write the follow-up in the register of the meeting. A team call gets a short message. A client call gets a formal recap. Lead with the decisions, keep the actions as a list, and put open questions last.
Never invent an owner or a deadline that nobody said. "No owner was named" is a useful line in a recap; a guessed name is a problem the user discovers in a week.
If the user wants the message sent, hand them the draft. Sending is theirs.
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.