New to Claude Skills? Learn how to install them →

anthropics on GitHub

Meeting Briefing

OfficialFree

Prepare structured legal meeting briefings and track actions.

Get this skill

Free · Opens the source repo

What Meeting Briefing does

The Meeting Briefing skill is designed specifically for in-house legal teams to streamline the preparation process for meetings that involve legal considerations. By gathering context from various connected sources, this skill helps users create structured briefings that outline essential information, ensuring that all legal aspects are covered before the meeting takes place. This is particularly useful for contract negotiations, board meetings, compliance reviews, and any other scenario where legal context is critical.

The skill operates through a systematic methodology that begins with identifying the meeting's context, including its title, type, participants, and agenda. It assesses the preparation needs based on the type of meeting, whether it’s a deal review, board meeting, or regulatory discussion. By pulling relevant information from calendars, emails, chat platforms, and documents, the skill synthesizes this data into a comprehensive briefing template, which includes details such as meeting objectives, participant roles, and key documents.

Additionally, the Meeting Briefing skill assists in tracking action items that arise during or after meetings. By organizing these tasks with clear ownership and deadlines, it helps ensure that follow-ups are managed effectively. This feature is vital for maintaining accountability within legal workflows and ensuring that nothing falls through the cracks.

While the skill is a powerful tool for preparing legal meetings, it is important to note that it does not provide legal advice. Users should review the generated briefings for accuracy and completeness before relying on them in a legal context. This skill is ideal for legal professionals who need to enhance their meeting preparation process and ensure that all relevant legal considerations are addressed.

When to use it

Use this skill when preparing for meetings that have legal implications, such as contract negotiations or compliance reviews, to ensure all necessary information is gathered and organized.

When not to use it

This skill is not suitable for meetings without legal relevance or for users seeking legal advice, as it does not offer legal counsel.

What you can build with it

Preparing for a Contract Negotiation

Use the skill to gather all necessary contract details, participant roles, and negotiation strategies before entering discussions.

Organizing a Board Meeting

Leverage the skill to compile legal updates, risk highlights, and pending matters to present to the board effectively.

Facilitating a Compliance Review

Utilize the skill to outline compliance status and relevant regulatory developments, ensuring all legal considerations are addressed.

How to install Meeting Briefing

View source

1. Install with the skills CLI

npx skills add anthropics/knowledge-work-plugins/meeting-briefing --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by anthropics

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 TypeKey Prep Needs
Deal ReviewContract status, open issues, counterparty history, negotiation strategy, approval requirements
Board / CommitteeLegal updates, risk register highlights, pending matters, regulatory developments, resolution drafts
Vendor CallAgreement status, open issues, performance metrics, relationship history, negotiation objectives
Team SyncWorkload status, priority matters, resource needs, upcoming deadlines
Client / CustomerAgreement terms, support history, open issues, relationship context
Regulatory / GovernmentMatter background, compliance status, prior communications, counsel briefing
Litigation / DisputeCase status, recent developments, strategy, settlement parameters
Cross-FunctionalLegal 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

Frequently asked questions about Meeting Briefing

Similar skills