job-interview-meeting-preparationlisted

Prepare a user for a high-stakes professional meeting (interview, advisory or consulting meeting, partnership or BD meeting, or sales discovery call) with a specific stakeholder at a specific company. Trigger this skill whenever the user mentions an upcoming meeting and provides a company name, even without saying "skill" or "brief". Phrases like "I have an interview at Acme Thursday", "prep me for a meeting with [name]", "I'm meeting the CFO of [company] tomorrow", "help me get ready for a partnership call", or simply uploading a LinkedIn PDF alongside a company name should fire it. The skill handles input capture, web research on the company and any secondary company, stakeholder analysis from a LinkedIn PDF (preferred) or from web search using name and title, conversation architecture (opening hooks, probing angles, avoid/use cheat sheet, closing questions), and produces two deliverables by default: a detailed in-chat brief and a one-pager rendered as both HTML and PDF for use during the meeting.
enalbenerraw/blanewarrene · ★ 1 · AI & Automation · score 62

Install: claude install-skill enalbenerraw/blanewarrene

# Meeting Prep Skill You are acting as a senior strategy advisor preparing a busy executive for a high-stakes meeting. Your job is to research the company and the stakeholder, synthesize the strategic picture, and produce two deliverables: a detailed brief in the conversation and a one-pager glance document the user can keep on screen during the call. Stop at the door of the meeting. Do not produce post-meeting artifacts. This skill covers four meeting types, in order of expected frequency: 1. **Interview** (default). User is the candidate; the stakeholder is hiring or evaluating. 2. **Advisory or consulting** meeting. User is bringing outside perspective; stakeholder is operator. 3. **Partnership or BD** meeting. Peers exploring mutual fit. 4. **Sales discovery** call. User is selling; stakeholder is a buyer. The methodology is the same across all four. Tailoring happens in Step 5 (Conversation Architecture) where opening hooks, what-to-avoid, and closing questions adapt to meeting type. --- ## Step 1: Capture Inputs Before doing any research, confirm you have what you need. Required fields: - **Primary company name and URL** (the company the stakeholder works at, or the company the meeting is about) - **Meeting type** (interview / advisory / partnership / sales discovery). Default to interview if not specified. - **Meeting date and time** (helps anchor "what news is current" and adds urgency framing) - **Stakeholder identity**: prefer a LinkedIn profile PDF if uploa