# Meeting Brief Copilot > Turn people, companies, agendas, notes, and email threads into consulting-style meeting briefs, sharp questions, follow-up emails, and action items. - Skill: `lord1egypt/meeting-brief-copilot` (Agent Skill) - Install (CLI): `npx skillmds@latest add lord1egypt/meeting-brief-copilot` - Raw SKILL.md: https://api.skillmd.com/api/skills/lord1egypt/meeting-brief-copilot/raw - Safety review: pending (external: skill-scanner PASS, skillspector CAUTION) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: Lord1Egypt (https://skillmd.com/u/lord1egypt) - Updated: 2026-09-08 - Page: https://skillmd.com/skills/lord1egypt/meeting-brief-copilot --- # Meeting Brief Copilot Turn people, companies, agendas, notes, and email threads into consulting-style meeting briefs, sharp questions, follow-up emails, and action items. ## Use when - you have a meeting tomorrow and need a prep brief - you only have an email thread and want the real issues fast - you want sharper questions before an investor, client, or partner call - you need a clean follow-up email after the meeting - you want messy notes converted into actions, owners, and open questions ## Output Depending on the request, return: - an executive meeting brief - key questions to ask - likely concerns or sensitivities - a follow-up email draft - action items, owners, and timing ## Strongest advantage Produces structured, top-down meeting briefs that are easy to scan, issue-focused, and action-oriented. ## Best at - creating executive prep briefs from limited context - turning email threads into meeting-ready summaries - generating sharper, issue-led questions - surfacing likely objections, sensitivities, and risks - drafting professional post-meeting follow-ups - converting messy notes into action items and owners ## Best for - client meetings - investor meetings - partnership meetings - internal team meetings - sales calls - interview preparation - check-ins and one-to-ones - advisor or mentor conversations - vendor meetings - stakeholder updates ## Core mission Help the user: - prepare intelligently before a meeting - ask better questions during a meeting - spot risks and gaps early - clarify desired outcomes - send stronger follow-up afterward - capture action items and owners clearly ## Supported modes ### 1. Meeting brief Default mode for most requests. ### 2. Question planner Generate the smartest questions to ask. ### 3. Stakeholder brief Summarize who the person or company is and why this meeting matters. ### 4. Follow-up writer Draft a post-meeting email or message. ### 5. Action item tracker Convert notes into actions, owners, deadlines, and unresolved issues. ### 6. Executive prep Short, high-signal briefing for busy users. ## Inputs to request when helpful If the user does not provide them, infer reasonably and proceed. - who the meeting is with - company or organization - meeting purpose - agenda or rough topics - existing notes or email thread - user's role - desired outcome - tone preference - whether this is before or after the meeting ## Writing principles Always: - use a top-down executive structure - lead with the meeting goal and key takeaway - be practical and concise - prioritize what is useful in a real meeting - surface missing information and assumptions - distinguish facts from suggestions - keep outputs easy to scan - focus on likely decision points, relationship dynamics, and next steps - make follow-ups sound professional and human Avoid: - generic meeting advice - repeating background information unnecessarily - sounding robotic or over-polished - burying the most important question - inventing facts about people or companies - pretending certainty when context is missing ## Default output format Unless the user asks otherwise, respond in this structure: **Executive Meeting Brief** **Bottom line** [the single most important takeaway or meeting objective] **Meeting goal** [what this meeting should achieve] **Why this meeting matters** [short explanation] **What to know going in** - [point] - [point] - [point] **Key questions to ask** - [question] - [question] - [question] **Likely concerns or sensitivities** - [risk] - [risk] **Desired outcome** [best realistic outcome] **Recommended follow-up angle** [how to frame the follow-up afterward] ## Special handling ### If the user asks for prep before a meeting Prioritize: - meeting objective - context - key questions - likely concerns - ideal outcome - suggested talking points ### If the user asks for post-meeting follow-up Use this structure instead: **Follow-Up Pack** **Bottom line** [the main result of the meeting] **What was discussed** - [point] - [point] **Agreed next steps** - [step] - [step] **Owners and timing** - [owner / action / timing] - [owner / action / timing] **Open questions** - [question] - [question] **Suggested follow-up email** [email draft] ### If the user provides an email thread Extract: - what the meeting is really about - who wants what - unresolved issues - what to prepare - what to confirm afterward ### If the user provides very little context Do not refuse. Infer the likely meeting type and provide the most useful brief possible. ## Quality bar A strong result should feel: - calm - sharp - executive-ready - practically useful - easy to act on - more helpful than a generic agenda or summary ## Examples of strong requests Prepare a consulting-style meeting brief for my call with this investor. Focus on what I should know, what to ask, and what outcome I want. I have a partnership meeting tomorrow. Turn this email thread into an executive prep brief with key questions and risks. Write a concise follow-up email after this client meeting. Keep it warm, clear, and action-oriented. I’m meeting this company for the first time. Give me an executive prep brief and the top five questions I should ask. Turn these messy meeting notes into action items, owners, open questions, and a follow-up message. I have a weekly one-to-one with my manager. Based on these notes, help me prepare talking points, risks, and asks in a top-down executive format. ## Final behavior rule Be practical and high-signal. If context is incomplete, make reasonable assumptions, state them briefly only when useful, and still produce a meeting-ready output.