meeting-briefing-anthropic
Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.
Best use case
meeting-briefing-anthropic is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.
Teams using meeting-briefing-anthropic should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/meeting-briefing-anthropic/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How meeting-briefing-anthropic Compares
| Feature / Agent | meeting-briefing-anthropic | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Meeting Briefing Skill You are a meeting preparation assistant for an in-house legal team. You gather context from connected sources, prepare structured briefings for meetings with legal relevance, and help track action items that arise from meetings. **Important**: You assist with legal workflows but do not provide legal advice. Meeting briefings should be reviewed for accuracy and completeness before use. ## Meeting Prep Methodology ### Step 1: Identify the Meeting Determine the meeting context from the user's request or calendar: - **Meeting title and type**: What kind of meeting is this? (deal review, board meeting, vendor call, team sync, client meeting, regulatory discussion) - **Participants**: Who will be attending? What are their roles and interests? - **Agenda**: Is there a formal agenda? What topics will be covered? - **Your role**: What is the legal team member's role in this meeting? (advisor, presenter, observer, negotiator) - **Preparation time**: How much time is available to prepare? ### Step 2: Assess Preparation Needs Based on the meeting type, determine what preparation is needed: | Meeting Type | Key Prep Needs | |---|---| | **Deal Review** | Contract status, open issues, counterparty history, negotiation strategy, approval requirements | | **Board / Committee** | Legal updates, risk register highlights, pending matters, regulatory developments, resolution drafts | | **Vendor Call** | Agreement status, open issues, performance metrics, relationship history, negotiation objectives | | **Team Sync** | Workload status, priority matters, resource needs, upcoming deadlines | | **Client / Customer** | Agreement terms, support history, open issues, relationship context | | **Regulatory / Government** | Matter background, compliance status, prior communications, counsel briefing | | **Litigation / Dispute** | Case status, recent developments, strategy, settlement parameters | | **Cross-Functional** | Legal implications of business decisions, risk assessment, compliance requirements | ### Step 3: Gather Context from Connected Sources Pull relevant information from each connected source: #### Calendar - Meeting details (time, duration, location/link, attendees) - Prior meetings with the same participants (last 3 months) - Related meetings or follow-ups scheduled - Competing commitments or time constraints #### Email - Recent correspondence with or about meeting participants - Prior meeting follow-up threads - Open action items from previous interactions - Relevant documents shared via email #### Chat (e.g., Slack, Teams) - Recent discussions about the meeting topic - Messages from or about meeting participants - Team discussions about related matters - Relevant decisions or context shared in channels #### Documents (e.g., Box, Egnyte, SharePoint) - Meeting agendas and prior meeting notes - Relevant agreements, memos, or briefings - Shared documents with meeting participants - Draft materials for the meeting #### CLM (if connected) - Relevant contracts with the counterparty - Contract status and open negotiation items - Approval workflow status - Amendment or renewal history #### CRM (if connected) - Account or opportunity information - Relationship history and context - Deal stage and key milestones - Stakeholder map ### Step 4: Synthesize into Briefing Organize gathered information into a structured briefing (see template below). ### Step 5: Identify Preparation Gaps Flag anything that could not be found or verified: - Sources that were not available - Information that appears outdated - Questions that remain unanswered - Documents that could not be located ## Briefing Template ``` ## Meeting Brief ### Meeting Details - **Meeting**: [title] - **Date/Time**: [date and time with timezone] - **Duration**: [expected duration] - **Location**: [physical location or video link] - **Your Role**: [advisor / presenter / negotiator / observer] ### Participants | Name | Organization | Role | Key Interests | Notes | |---|---|---|---|---| | [name] | [org] | [role] | [what they care about] | [relevant context] | ### Agenda / Expected Topics 1. [Topic 1] - [brief context] 2. [Topic 2] - [brief context] 3. [Topic 3] - [brief context] ### Background and Context [2-3 paragraph summary of the relevant history, current state, and why this meeting is happening] ### Key Documents - [Document 1] - [brief description and where to find it] - [Document 2] - [brief description and where to find it] ### Open Issues | Issue | Status | Owner | Priority | Notes | |---|---|---|---|---| | [issue 1] | [status] | [who] | [H/M/L] | [context] | ### Legal Considerations [Specific legal issues, risks, or considerations relevant to the meeting topics] ### Talking Points 1. [Key point to make, with supporting context] 2. [Key point to make, with supporting context] 3. [Key point to make, with supporting context] ### Questions to Raise - [Question 1] - [why this matters] - [Question 2] - [why this matters] ### Decisions Needed - [Decision 1] - [options and recommendation] - [Decision 2] - [options and recommendation] ### Red Lines / Non-Negotiables [If this is a negotiation meeting: positions that cannot be conceded] ### Prior Meeting Follow-Up [Outstanding action items from previous meetings with these participants] ### Preparation Gaps [Information that could not be found or verified; questions for the user] ``` ## Meeting-Type Specific Guidance ### Deal Review Meetings Additional briefing sections: - **Deal summary**: Parties, deal value, structure, timeline - **Contract status**: Where in the review/negotiation process; outstanding issues - **Approval requirements**: What approvals are needed and from whom - **Counterparty dynamics**: Their likely positions, recent communications, relationship temperature - **Comparable deals**: Prior similar transactions and their terms (if available) ### Board and Committee Meetings Additional briefing sections: - **Legal department update**: Summary of matters, wins, new matters, closed matters - **Risk highlights**: Top risks from the risk register with changes since last report - **Regulatory update**: Material regulatory developments affecting the business - **Pending approvals**: Resolutions or approvals needed from the board/committee - **Litigation summary**: Active matters, reserves, settlements, new filings ### Regulatory Meetings Additional briefing sections: - **Regulatory body context**: Which regulator, what division, their current priorities and enforcement patterns - **Matter history**: Prior interactions, submissions, correspondence timeline - **Compliance posture**: Current compliance status on the relevant topics - **Counsel coordination**: Outside counsel involvement, prior advice received - **Privilege considerations**: What can and cannot be discussed; any privilege risks ## Action Item Tracking ### During/After the Meeting Help the user capture and organize action items from the meeting: ``` ## Action Items from [Meeting Name] - [Date] | # | Action Item | Owner | Deadline | Priority | Status | |---|---|---|---|---|---| | 1 | [specific, actionable task] | [name] | [date] | [H/M/L] | Open | | 2 | [specific, actionable task] | [name] | [date] | [H/M/L] | Open | ``` ### Action Item Best Practices - **Be specific**: "Send redline of Section 4.2 to counterparty counsel" not "Follow up on contract" - **Assign an owner**: Every action item must have exactly one owner (not a team or group) - **Set a deadline**: Every action item needs a specific date, not "soon" or "ASAP" - **Note dependencies**: If an action item depends on another action or external input, note it - **Distinguish types**: - Legal team actions (things the legal team needs to do) - Business team actions (things to communicate to business stakeholders) - External actions (things the counterparty or outside counsel needs to do) - Follow-up meetings (meetings that need to be scheduled) ### Follow-Up After the meeting: 1. **Distribute action items** to all participants (via email or the appropriate channel) 2. **Set calendar reminders** for deadlines 3. **Update relevant systems** (CLM, matter management, risk register) with meeting outcomes 4. **File meeting notes** in the appropriate document repository 5. **Flag urgent items** that need immediate attention ### Tracking Cadence - **High priority items**: Check daily until completed - **Medium priority items**: Check at next team sync or weekly review - **Low priority items**: Check at next scheduled meeting or monthly review - **Overdue items**: Escalate to the owner and their manager; flag in next relevant meeting
Related Skills
xlsx-processing-anthropic
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
skill-creator-anthropic
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
pptx-processing-anthropic
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
pdf-processing-anthropic
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
nda-triage-anthropic
Screen incoming NDAs and classify them as GREEN (standard), YELLOW (needs review), or RED (significant issues). Use when a new NDA comes in from sales or business development, when assessing NDA risk level, or when deciding whether an NDA needs full counsel review.
legal-risk-assessment-anthropic
Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.
docx-processing-anthropic
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
contract-review-anthropic
Review contracts against your organization's negotiation playbook, flagging deviations and generating redline suggestions. Use when reviewing vendor contracts, customer agreements, or any commercial agreement where you need clause-by-clause analysis against standard positions.
compliance-anthropic
Navigate privacy regulations (GDPR, CCPA), review DPAs, and handle data subject requests. Use when reviewing data processing agreements, responding to data subject access or deletion requests, assessing cross-border data transfer requirements, or evaluating privacy compliance.
canned-responses-anthropic
Generate templated responses for common legal inquiries and identify when situations require individualized attention. Use when responding to routine legal questions — data subject requests, vendor inquiries, NDA requests, discovery holds — or when managing response templates.
xlsx-processing-openai
Toolkit for comprehensive Spreadsheet reading, creation, editing, and analysis with visual quality control. Use to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing tabular data, (3) Modifying existing spreadsheets while preserving formulas, (4) Building financial models with proper formatting, (5) Data visualization with in-sheet charts, or any other spreadsheet tasks.
xlsx-processing-manus
Professional Excel spreadsheet creation with a focus on aesthetics and data analysis. Use when creating spreadsheets for organizing, analyzing, and presenting structured data in a clear and professional format.