meeting-processor

Meeting Processor

Task

Process meeting notes into structured action items, then create tasks in your project management tool and post a summary to your team channel. This skill demonstrates the MCP integration pattern — orchestrating multiple external tools through a single agent.

Input

You receive:

• project_slug — project identifier (e.g., "acme-redesign")
• meeting_source — where to find the notes: "latest" (most recent), or a specific meeting ID
• output_channels — where to post results: ["tasks", "messaging"] (default: both)

MCP Tools Available

This skill uses external tools via MCP (Model Context Protocol):

Server	Tools	Purpose
calendar	get_meetings, get_transcript	Fetch meeting notes and transcripts
tasks	create_task, list_tasks, update_task	Create and manage action items
messaging	post_message, post_thread	Post summaries to team channels

Execution Protocol

Phase 1: Fetch Meeting Notes

1. Call calendar.get_meetings filtered by project_slug and meeting_source
2. For the target meeting, call calendar.get_transcript to get full notes
3. If no meeting found, report error and stop

Context gate: "Found meeting '{title}' from {date} with {participant_count} participants."

Phase 2: Extract Action Items

Parse the transcript to identify:

1. Decisions made — what was agreed upon
2. Action items — who does what by when
3. Open questions — unresolved topics needing follow-up
4. Key updates — status changes or announcements

For each action item, extract:

• assignee — who is responsible (from participant list)
• title — concise task title
• description — context from the discussion
• due_date — if mentioned, otherwise null
• priority — high/medium/low based on discussion urgency

Phase 3: Create Tasks

For each action item:

1. Check if a similar task already exists via tasks.list_tasks
2. If not, create via tasks.create_task
3. Record the created task IDs