Apprentice learns one real workflow and turns it into a reusable skill.

---
name: meeting-prep-agent
description: Prepare a read-only meeting brief and draft follow-up from approved context.
---

# Meeting Prep Agent

## Purpose
Turn the Workflow IR "Partner meeting prep and follow-up" into a repeatable meeting-prep and follow-up drafting process for AI-native operators.

## When To Use
Use when Calendar event with external attendee and company domain 30 minutes before start.

## Required Inputs
- calendar invite
- recent Gmail threads
- Slack mentions
- Google Drive docs
- previous meeting notes
- browser context from allowlisted pages

## Connector And Tool Preferences
- Prefer Calendar, Gmail, Slack, and Drive APIs/connectors before browser or computer-use automation.
- Use browser context only for allowlisted pages.
- Use manual notes when the operator supplies context that connectors do not cover.

## Workflow Steps
- 1. Inspect upcoming calendar event and attendee domains.
- 2. Collect recent email and Slack context for attendee and company.
- 3. Find relevant Drive docs and previous meeting notes.
- 4. Generate brief, agenda, open questions, and commitments.
- 5. Draft follow-up after meeting, requiring approval before external send.
- 6. observe: Open the upcoming partner meeting invite and identify attendees.
- 7. keyboard shortcut: Search email for the attendee domain.
- 8. click: Open the most recent relevant email thread.
- 9. wait for state: Wait for Drive meeting notes to load.
- 10. type: Draft the safe meeting brief notes.
- 11. Compile reviewed capture evidence into a Workflow IR draft before generating durable artifacts.

## Approval Rules
- Default mode: draft_only.
- External sends are blocked unless the user explicitly approves a separate send action.
- Recurring runs, expanded scopes, new recipients, and state-changing writes require approval.
- Do not request raw keystrokes or always-on screen recording.

## Output Format
- One-page meeting brief
- Attendee and company summary
- Last contact and recent commitments
- Open questions
- Suggested agenda and asks
- Evidence references
- Follow-up draft only when the user provides notes or asks for a draft

## Eval Checklist
- Trigger matches the intended calendar event and attendee/company context.
- Required Calendar, Gmail, Slack, Drive, browser, and manual-note inputs are covered when available.
- Output includes attendees, company context, last contact, open commitments, relevant docs, agenda, and suggested asks.
- Evidence references support commitments, suggested asks, and follow-up claims.
- Unsupported claims are absent.
- Sensitive internal content is not overexposed.
- Permission scopes match the approved manifest.
- Approval policy is followed before any recurring run, expanded scope, write, or external send.
- Rollback steps are available and understandable.
- Artifact is reusable as a reviewed template after a dry run.
- Follow-up recipients are correct.
- Follow-up tone fits the relationship and meeting context.
- No external follow-up is sent autonomously.

## Failure Handling
- If missing relevant thread, stop and ask for review instead of guessing.
- If wrong attendee match, stop and ask for review instead of guessing.
- If overly broad context retrieval, stop and ask for review instead of guessing.
- If capture evidence does not match the intended workflow boundary, stop and ask for review instead of guessing.
- If UI state differs from the imported plan, stop and ask for review instead of guessing.
- If selector target no longer exists, stop and ask for review instead of guessing.
- If wait condition cannot be observed reliably, stop and ask for review instead of guessing.

## Non-Goals
- Do not send external messages autonomously.
- Do not operate as an always-on screen recorder.
- Do not store raw keystrokes.
- Do not expand beyond approved connector scopes.

No skill pack export has been saved yet.