meeting-followup
Skill9 starsChanged 3 months agoMITView on GitHub
Use when a meeting has been completed and you need to generate follow-up emails, when processing meeting notes to extract next steps and objections, or when routing post-meeting tasks based on meeting outcome
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
- lexvalo/riverscript-claude-plugintheir own version, first seen Oct 1, 2026
- cyxar4uk/ya360-mcptheir own version, first seen Sep 27, 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
- 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
- lexvalo/riverscript-claude-plugin★ 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- champion-trackerSkill
- compliance-managerSkill
- contact-finderSkill
- deliverability-managerSkill
- email-writerSkill
- linkedin-contentSkill
- multi-channel-writerSkill
- pipeline-trackerSkill
- prospect-researcherSkill
- resource-offerSkill
- setupSkill
- signal-scannerSkill
- validateSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
Keep subject lines under 50 characters
- Very specific: line 56
Stakeholder tasks: if stakeholders_needed is non-empty, create a task to arrange intro
- Very specific: line 57
Re-qual flag: if outcome is negative, set reminder for 6 months
“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
Meeting Follow-Up
Input
Provide one of:
- Free-text meeting notes (transcript excerpt, CRM note, bullet points)
- Structured
MeetingOutcomerecord fromscripts/models.py
Required fields: deal ID or company name, meeting date, attendees, outcome signal.
Step 1: Extract Structured Data
From notes, extract and populate a MeetingOutcome record:
| Field | What to look for |
outcome | Buying signal ("loved it", "interested") → positive; polite but vague → neutral; "not now", "no budget" → negative; no attendance → no_show |
objections | Any hesitation, technical concern, or blocker raised |
next_steps | Explicit commitments or asks from either party |
decision_timeline | Any deadline or review window mentioned |
stakeholders_needed | Names or roles needed for sign-off |
follow_up_resources | Docs, case studies, or demos promised |
Step 2: Select Template Sequence
Load config/templates/email-sequences/meeting-followup.md and select the block matching outcome:
positive→ 3-email sequence (Day 0, 3, 7)neutral→ 3-email sequence (Day 0, 5, 14)negative→ 1 email only; flag for 6-month re-qualificationno_show→ 2-email sequence (Day 0, 3)
Step 3: Generate Follow-Up Emails
For each email in the sequence:
- Fill all
{{placeholders}}with data fromMeetingOutcome - Reference specific objections by name — never use generic language
- Tie resources to what was discussed, not generic product features
- Keep subject lines under 50 characters
- CTA must be low-friction: calendar link, async resource, or a direct question
Voice rules (from config/gtm-context.md): no "just checking in", no "hope this finds you well", no unsolicited demo asks.
Step 4: CRM and Sequencing Recommendations
Output a CRM action block:
- Stage update: advance
DealStagetoMEETING_COMPLETED - Next touch date: Day 0 email send date + sequence cadence
- Stakeholder tasks: if
stakeholders_neededis non-empty, create a task to arrange intro - Re-qual flag: if
outcomeisnegative, set reminder for 6 months
Output Format
## MeetingOutcome Record
[populated record]
## Follow-Up Sequence ([outcome])
### Email 1 — Day 0
Subject: ...
Body: ...
### Email 2 — Day N (if applicable)
...
## CRM Actions
- Stage: MEETING_COMPLETED
- Next touch: [date]
- Tasks: [list]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.

