Prepare For Meeting

Skill Configuration

User Context

• Invoke sales:user-context in preflight mode by loading [$sales:user-context](../user-context/SKILL.md) and running its preflight script before searching connectors, retrieving evidence, or drafting output. Do not look for a callable MCP tool named sales:user-context.
• Use the returned sales_preflight envelope as authoritative for saved context, source-category mapping, final obligations, and conditional guidance.
• Apply hard final_obligations unless the response is clarification-only.
• Apply context_gap_note only when missing setup or inaccessible sources materially limits the brief.

Audience And Language

Source Resolution

Required Inputs

• [required] Company, account, key attendee, meeting title, invite, or date/time
• [required] Meeting attendees or attendee organizations
• [required] Meeting goal, agenda, topic, or meeting type
• Past context, transcripts, notes, emails, docs, or CRM context when available

• If a required input is missing or ambiguous, use Fast Candidate Resolution: make at most 3 total tool calls before asking the user to choose, including mandatory Sales preflight. Search only to produce useful concrete defaults, then ask the user to confirm or supply that required input before drafting.
• Treat ambiguous company-like proper nouns, partner names, and account shorthands as possible customer/account anchors unless the request clearly indicates an internal-only person, product, or topic. When crm is available, include a bounded CRM lookup before relying on calendar, docs, internal messages, meeting notes, or public context alone. If CRM returns one high-confidence account match, use it as the primary account candidate; if multiple plausible account matches remain, ask the user to choose from concrete candidates.
• Before asking the user to name a meeting, paste an invite, or provide attendee/agenda details, first try the workflow source category that owns the missing meeting anchor: calendar for meeting candidates, titles, attendees, timing, invite body, and agenda. For customer/account ambiguity, try crm before relying on document_store, internal_messaging, meeting_notes, or public context alone. Manual meeting details are the fallback after those categories are unavailable, empty, or insufficient.
• User confirmation is required for any required input inferred from sources rather than provided by the user.
• When asking, present up to 5 concrete candidates with one-line rationale. Make lettered options usable as reply targets, but omit a separate reply-with-letter footer when the choices are already clear.

{Natural clarification question, e.g. "Which meeting should I prepare?"}

a. **{actual candidate}** - {short source-derived context}
b. **{actual candidate}** - {short source-derived context}

Workflow Sources

• calendar: meeting existence, meeting title, time, attendees, invite body, stated agenda, and first-pass meeting focus.
• crm: account status, opportunity/deal context, contacts, owner, recent activity, and account records that materially change meeting prep.
• meeting_notes: prior calls, internal prep calls, objections, stakeholder language, commitments, decisions, follow-ups, and transcript-backed continuity.
• document_store: account plans, implementation docs, mutual action plans, relevant assets, account notes, and team guidance.
• external_messaging: recent customer questions, commitments, attachments, tone shifts, scheduling context, and promised next steps.
• internal_messaging: account-team strategy, risks, blockers, internal coordination context, and discussion history that changes how the meeting should be handled.
• data_enrichment / public web search: company/contact enrichment, attendee roles, firmographics, official company context, recent news, filings, announcements, funding, earnings, leadership changes, and first-time account ramp-up. Use public web only after a meeting/account anchor exists, keep searches targeted to the anchored company, attendees, and topic, and skip it when internal sources already provide enough context.

• For next, upcoming, today, tomorrow, scheduled, daily-digest, or invite-dependent meeting prep, calendar is required to resolve the meeting title, time, attendees, invite body, and stated agenda unless the user supplied equivalent meeting details. For vague prompts such as "prep me for a meeting" or "prep me for my next meeting," stop after calendar candidate discovery and return options; enrichment starts only after user selection. If calendar is unavailable but user-provided details are sufficient, continue with a clear limitation; if the meeting anchor remains ambiguous, ask with concrete calendar-backed candidates when available.
• Do not infer a calendar-selected meeting from crm, external_messaging, internal_messaging, document_store, meeting_notes, public web, or enrichment. Those sources may suggest candidate context, but selected meeting evidence still needs calendar, user-provided details, or user confirmation.
• For customer/account meetings, meeting_notes is conditional but expected when accessible and likely to contain prior customer or internal prep context. Search by account, attendee, meeting title, and opportunity/topic terms. If checked and no relevant prior context is found, say so briefly instead of implying transcript-backed continuity.
• For customer/account meetings, crm is required when CRM is available and a customer/account anchor is supplied, inferred, or confirmed. Use CRM for account status, opportunity/deal context, owner, contacts, recent activity, and records that materially change the agenda, risks, recommended close, or broader account posture. When multiple opportunities or solutions exist, prefer the one that matches the meeting title/topic, user ask, attendees, product or solution aliases, and recency. If CRM is unavailable or yields no relevant account/deal context, name the gap.
• Do not run every source by default. Stop once the meeting anchor is resolved and the brief has enough high-value evidence; name unchecked or unavailable optional sources as limitations or expansion opportunities when they could matter.

• Use each source category for the facts it owns; do not substitute mirrored sources, browser UI, Computer Use, or web search for authoritative connector evidence.
• Do not treat calendar, docs, Slack/internal messaging, email, meeting notes, public context, or third-party enrichment as substitutes for CRM-owned customer truth.
• Treat public web as lower-authority enrichment after a meeting/account anchor exists; do not use it to invent private account status, commitments, objections, support posture, or deal facts.
• If a source is unavailable, blocked, stale, ambiguous, or missing required fields, name the gap and either ask for access/input, proceed with a clear limitation, or omit the unsupported claim.
• Do not wait on optional enrichment once the meeting is anchored and the available evidence is enough for a useful prep brief; continue with a labeled limitation.
• If continuity is thin, say so and use public/company context only as first-time ramp-up, with Inference: for synthesis.
• If evidence is weak or only broadly sourced, omit it or place it in background rather than turning it into tactical guidance.

Context Gathering Principles

• Start with the canonical source and narrowest scope.
• Gather evidence that materially improves the answer.
• Take the 80/20 path when it gives a useful, grounded result.
• Broaden only when the first pass is empty, thin, or misleading.
• Answer once the core artifact is supported; name limitations and offer expansion options.

First-Run Banner

## Prepare For Meeting
This skill creates a concise brief for an upcoming customer or high-value sales-adjacent meeting using calendar, account context, CRM, meeting notes, transcripts, docs, email, internal messaging, saved plugin memory, and user-provided guidance.

Next Step Guidance

Final Continuation Invariant

Journey States

Post-Meeting Reminder

Daily Meeting Prep Automation

Acceptance Handling

Context Sufficiency

• Do not stop after the first available source when another accessible source could materially change the agenda, risk framing, account posture, recommended close, or next action.
• Prefer high-value evidence gathering during research and tighter synthesis in the final brief.
• Use as much direct, high-signal context as is helpful for confidence, but include only the highest-leverage facts, gaps, and inferences in the user-facing output.
• When time, access, or source availability limits context gathering, name the limitation and its likely impact.

Search Discipline And Yielding

• Start with the source categories most likely to change the meeting objective, agenda, risks, close, or next action.
• For each attempted source, use targeted queries and stop after useful evidence, a clear no-result, or two failed attempts.
• Do not chase indirect, mirrored, or convoluted paths to reconstruct unavailable source truth; use Authority and gaps.
• If repeated errors, auth gaps, rate limits, ambiguity, or missing access block reliable prep, stop searching and tell the user the core issue, what evidence is available, and the shortest unblock option.
• Prefer a limited brief with Known Limitations or a concise clarification over long-running retrieval.

Prep Modes

1. Single Meeting Prep: use when the user asks for prep for one specific customer meeting, account, invite, attendee, or topic.
2. Daily Prep Digest: use when the user asks for a day-based summary or morning prep digest. Start from calendar, keep meetings with at least one external attendee, and produce one chronological digest.
3. Scheduled Meeting Selection: use only for system-triggered automations, heartbeats, recurring check-ins, or scheduled runs. Start from calendar, prepare exactly one meeting where prep would materially help, briefly say why it was selected, and return DONT_NOTIFY if no qualifying meeting exists. Choose among candidates using the strongest available impact signals:

• customer or prospect importance;
• executive or buyer attendance;
• late-stage opportunity or renewal context;
• explicit agenda urgency;
• unresolved risk or decision topics;
• strategic account status;
• recent customer-facing activity;
• high-stakes internal decision-making;
• launch or product dependencies;
• leadership visibility;
• whether a prep brief would improve the user's next action.

Procedure

1. Start from the meeting source. Use calendar for day-based, scheduled, invite-dependent, or user-requested calendar selection, including next, upcoming, today, tomorrow, or latest scheduled meeting prompts. Read title, timing, attendee list, description, and invite body before adding narrative unless the user supplied equivalent meeting details.
2. Qualify the meeting for the active prep mode. For Single Meeting Prep and Daily Prep Digest, keep the customer/account anchor and stop if the meeting is not clearly customer-facing or account-related. For Scheduled Meeting Selection, customer/account meetings win; otherwise choose only a high-impact non-routine work meeting. For non-customer meetings selected only by Scheduled Meeting Selection, do not add customer-specific objections, CRM facts, public account research, customer-facing assets, or Broader Account Context unless the meeting evidence actually names a customer or account.
3. Define a one-sentence focus hypothesis before gathering supporting context. Use the invite title/body, user-supplied target, attendee roles, recent scheduling or email context, internal discussion that references this meeting or a same-day call, and current account workstreams. Use the hypothesis to prioritize sources, not to exclude strong contrary evidence.
4. Explain attendee relevance for single-meeting briefs. Identify external attendees first; include sourced roles or history when reliable. Group internal attendees by role or relevance when individual titles are not sourced. Do not guess titles; say when only email identity is known.
5. Pull current account or workstream state. For customer/account meetings, use crm and document_store for account state and broader context. Match the active opportunity or deal to the meeting topic before using deal facts; if another same-account opportunity appears unrelated, exclude it or label the conflict instead of letting it drive the brief. Capture account-level facts for Broader Account Context; promote them into Upcoming Meeting only when they directly affect the objective, agenda, risks, questions, or close. For non-customer meetings selected by Scheduled Meeting Selection, use internal sources for workstream decisions, blockers, owners, and dependencies instead of forcing account context.
6. Pull continuity and recent context. Search meeting_notes by exact external attendee emails or names, account name and aliases, opportunity or solution names, invite title terms, and focused topic terms. If no direct prior external customer call is found, say so and use relevant internal meeting records only as internal continuity. Then pull external_messaging for unanswered questions, scheduling shifts, tone changes, and promised next steps. Then pull internal_messaging and document_store for internal strategy that changes the agenda, decision framing, likely objections, or next actions.
7. Run a concise public web enrichment pass only when it materially improves preparation. Useful targets include high-confidence external attendee title/company matches, official company or product pages, public customer pages, product or partnership announcements, filings, earnings, funding, leadership changes, and reputable news. If internal continuity is thin, label the brief as first-time or low-context and add public ramp-up context with Inference: where needed. If public evidence conflicts with internal sources, defer to internal source truth and mention the discrepancy in Known Limitations.
8. Focus the agenda. Use invite agenda when present; otherwise recommend a short agenda based on the focus hypothesis and strongest current signals. Broad account-plan items enter the focused agenda only when another strong signal ties them to this meeting, such as the invite, attendee roles, recent message context, prior continuity, a same-day customer call, or a recent note assigning owners.
9. Add a light two-sided alignment frame when needed. Use one when a topic involves disagreement, unclear ownership, incompatible expectations, or negotiation around pricing, capacity, data retention, support, roadmap commitments, co-sell, procurement, security, implementation ownership, or executive sensitivity. Use the compact shape Problem, Customer side, Seller side, and Goal for this meeting; name people only when sourced and label inferred motives or constraints.
10. Recommend up to 3 existing customer-facing assets to bring. Explain why each helps. Do not fabricate, generate, or rewrite assets in this skill.
11. Cite tactical claims and separate facts from synthesis. For normal single-meeting briefs, put citations inline on the Background Context bullets instead of collecting them in a separate sources section. Each factual Background Context bullet should end with the source title, record name, channel/thread, or meeting/date label as visible Markdown link text when a source exposes a useful URL. Use plain labels with (no useful link available) when needed. Do not link to meeting join URLs, generic room links, or opaque connector refetch IDs.
12. Assemble the final answer against Output Shapes before sending. Select the applicable provided shape after the prep mode and meeting type are known, then fill that shape directly. The selected output shape is the only user-facing structure for the brief body; after it, apply Next Step Guidance unless an explicit exception applies.

Output Shapes

# [Meeting Name]

**Date:** [Date / Time]
**Attendees:** [Names + roles]

## Summary

* [Core meeting objective]
* [Current account, opportunity, or workstream signal]
* [Top implication, risk, or source gap for this meeting]

## Goal

[The specific outcome to achieve: decision, feedback, alignment, commitment, or next step.]

## Open Questions

* [Most important unresolved question]
* [Question this meeting should answer, tied to CRM, transcript, or invite gaps when relevant]
* [Decision or clarification needed]

## Proposed Agenda

1. [Topic or question to discuss]
2. [Topic or decision to resolve, tailored to meeting type and deal/workstream stage]
3. [Confirm next steps / owners]

## Background Context

* [Compact account/deal or workstream snapshot with inline source citation]
* [Relevant attendees, prior-call/internal-prep continuity, or customer/team context with inline source citation]
* [Useful assets, constraints, and material source gaps with inline source citation when factual]

• Clarification Stop: end with only the unresolved required input question.
• Daily Prep Digest: use **Today's External Meetings**, one compact chronological brief per meeting, and **Priority Watchouts**.