meeting-recap-email
Skill1 starsChanged 7 months agoNo licenceView on GitHub
Generate a professional email recap of a meeting and draft it to the attendees. Trigger on 'recap that meeting', 'send a recap', 'meeting follow-up email', 'summarize the meeting and email it', 'write a recap to the attendees', 'draft a follow-up from that call', 'send meeting notes', 'email the recap', 'recap email', 'post-meeting email', 'send the attendees a summary', or when the user provides a transcript and says 'turn this into a follow-up email'. Also trigger for partial requests like 'follow up from that call'. Pulls attendees from Google Calendar, extracts decisions and action items from transcripts/notes, and drafts via message_compose or Gmail. Do NOT use for deep call analysis or PDF reports (use analyze-call) or pre-meeting briefs (use account-brief-generator).
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- account-brief-generatorSkill
- ai-fluency-assessmentSkill
- anyreach-deck-pptxSkill
- anyreach-financial-reportSkill
- anyreach-funnel-analysisSkill
- anyreach-web-designSkill
- bpo-partner-pitch-deckSkill
- bpo-roi-briefSkill
- bpo-roi-internal-briefingSkill
- bpo-roi-modelSkill
- brand-style-extractorSkill
- callsSkill
- company-deep-researchSkill
- competitor-deep-diveSkill
- consumer-intelligence-xlsxSkill
- consumer-intel-reportSkill
- cx-intel-report-pdfSkill
- cx-intel-report-xlsxSkill
- demo-bot-usage-reportSkill
- deploy-intelSkill
- discovery-dashboardSkill
- discovery-to-proposalSkill
- gtm-audit-appSkill
- gtm-audit-pdfSkill
- gtm-stack-auditSkill
- legal-reviewSkill
- leverage-analysisSkill
- maturity-assessmentSkill
- narrative-deckSkill
- portfolio-cx-briefSkill
- product-site-frameworkSkill
- proposal-sow-generatorSkill
- remotion-best-practicesSkill
- reviews-vs-live-callsSkill
- richard-thought-leadershipSkill
- shadcn-deckSkill
- stakeholder-intelSkill
- status-deckSkill
- visual-briefSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. About 0 are common, 21 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈21
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

