Prepare For Meeting

Prepare a seller or account director for an upcoming customer meeting, or for the most important meeting of the day in scheduled mode. Optimize for the meeting in front of the user: agenda, decisions, high-priority topics, likely blockers, and next actions. Keep broader account context short and subordinate.

A single-meeting brief must use the provided Output Shapes format exactly. Fold broader account, product, deal, support, partnership, or public-company context into Background Context only when it changes how the user should handle the meeting.

Use this skill primarily for customer-facing or account-related meetings. In scheduled mode, prefer customer/account meetings; if none qualify, choose only the most important non-routine work meeting where prep would materially help. Do not choose routine internal team meetings, 1:1s, interviews, performance conversations, or generic meetings unless the user explicitly asks or the evidence shows clear business stakes.

Skill Configuration

User Context

Mandatory pre-answer gate:

• 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.