Generates personalized follow-up emails after meetings or events, extracting action items and sending individualized messages to each responsible party. [EXPLICIT] Trigger: "follow up", "seguimiento", "send follow-up", "action items email"
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdknowledge/follow-up-best-practices.mdtemplates/follow-up-action-items.mdGenerates personalized follow-up emails after meetings or events. Extracts action items from meeting notes and sends individualized messages to each responsible party with only their relevant tasks, deadlines, and context. [EXPLICIT]
This skill activates when the user: [EXPLICIT]
Parse the meeting notes (provided as text, file, or document link) to identify: [EXPLICIT]
Parsing rules:
For each attendee with action items: [EXPLICIT]
templates/follow-up-action-items.md templatePersonalization rules:
When deadlines are identified: [EXPLICIT]
mcp__workspace-mcp__manage_event to create remindersDefault behavior: draft first, send after user approval. [EXPLICIT]
mcp__workspace-mcp__draft_gmail_message to create draftsmcp__workspace-mcp__send_gmail_message to sendSafety rules:
| Criterion | Requirement |
|---|---|
| Completeness | Every action item from notes appears in exactly one email |
| Accuracy | Correct assignee for each task, correct deadlines |
| Privacy | No person sees another person's action items |
| Tone | Professional, warm, actionable — not robotic |
| Timing | Follow-up sent within 24h of meeting (best practice) |
| Template | Uses branded template consistently |
| Confirmation | User approves before any email is sent |
| Anti-Pattern | Correct Approach |
|---|---|
| Sending all action items to everyone | Personalize: each person gets only their items |
| Auto-sending without review | Always draft first, send after approval |
| Vague action items ("handle the thing") | Preserve original specificity from notes; flag vague items |
| Missing deadlines | If no deadline specified, flag and ask user |
| Generic greeting ("Dear team member") | Use attendee's actual first name |
| Ignoring meeting context | Include relevant decisions that affect each task |
| Sending to people with no action items | Skip attendees with zero items (or send optional summary-only) |
| Agent | Role |
|---|---|
| Lead | Parses meeting notes, extracts action items, generates email content |
| Support | Formats emails, applies templates, handles calendar event creation |
| Guardian | Validates completeness (all items assigned), privacy (no cross-leak), tone |
| Specialist | Email deliverability, personalization optimization, multi-language support |
Meeting: Q2 Planning - April 1, 2026
Attendees: Ana (ana@company.com), Carlos (carlos@company.com), Maria (maria@company.com)
Decisions:
- Budget approved for new marketing campaign
- Launch date set for May 15
Action items:
- Ana: Prepare campaign brief by April 8
- Carlos: Set up analytics dashboard by April 10
- Carlos: Review vendor proposals by April 5
- Maria: Schedule kickoff with design team by April 4
- Maria: Draft social media calendar by April 12
Three personalized emails, each containing only the recipient's items, with meeting context and next steps.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.