Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot official · Anthropic

meeting-briefing — Claude Code skill: what it does, how to install

Prepares structured briefings for legally sensitive meetings and tracks follow-up action items. It pulls context from emails, chats, documents, and calendars before you join the room.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add anthropics/knowledge-work-plugins --skill meeting-briefing -a claude-code
Open on GitHub

What meeting-briefing does

The skill organizes context for meetings where legal details matter. It looks at the meeting type, attendee list, agenda, and your role as a legal team member. From there, it gathers details across connected sources like calendar invites, email threads, chat channels in Slack or Teams, and document repositories.

Everything feeds into a standard briefing document. It maps out background history, open issues, discussion points, decisions required, and non-negotiable positions for negotiations. If a document cannot be found or data looks outdated, the assistant flags those gaps in a dedicated section.

This assistant supports in-house legal workflows but does not provide legal advice. That makes human review of the generated briefing necessary before every call.

What it helps with

  • compile a briefing packet for contract negotiations
  • gather participant context and open issues for board meetings
  • identify non-negotiable positions and talking points
  • track action items and unresolved topics from prior calls

Example prompts for the agent

  • Prepare a meeting brief for tomorrow's vendor contract review call
  • Gather context from email and calendar for the upcoming board meeting
  • Create a briefing for our regulatory discussion, including background and open issues

How to install meeting-briefing

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/meeting-briefing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/meeting-briefing/

From the same set89

The whole set →
data-visualization official anthropics Selects chart types based on data structure and produces Python visualization code in matplotlib, seaborn, and plotly. Useful for reports and research figures. Claude Code CX Codex Cursor +1 13,700installs documentation official anthropics A skill for technical writing that drafts READMEs, API references, runbooks, architecture docs and onboarding guides. Useful when the code exists but the description does not. Claude Code CX Codex Cursor +1 10,300installs build-dashboard official anthropics Builds a self-contained HTML dashboard with Chart.js charts, KPI cards, and filterable tables. Useful for turning raw data or queries into a standalone browser report. Claude Code CX Codex Cursor +1 9,100installs memory-management official anthropics This skill organizes workplace shorthand, names, and project details into files an agent can consult. It fits projects where requests rely on an internal vocabulary and shared context. Claude Code CX Codex Cursor +1 7,400installs task-management official anthropics Tracks commitments, active work, and follow-ups in a local TASKS.md file. Useful when managing project to-dos directly from the AI coding chat. Claude Code CX Codex Cursor +1 7,200installs architecture official anthropics Writes an Architecture Decision Record or reviews a system design: options, trade-offs, consequences. Useful when you have to pick between technologies. Claude Code CX Codex Cursor +1 6,700installs knowledge-synthesis official anthropics Merges search results across chats, emails, and documents into deduplicated answers with source attribution. Flags conflicting facts and scores source reliability. Claude Code CX Codex Cursor +1 6,400installs testing-strategy official anthropics This skill designs testing strategies and test plans for a project. Use it when you need test types, coverage goals, or gaps in existing checks. Claude Code CX Codex Cursor +1 6,400installs

Similar

Questions about meeting-briefing

How to install meeting-briefing in Claude Code?

Run npx skills add anthropics/knowledge-work-plugins --skill meeting-briefing -a claude-code in your terminal.

What types of meetings does meeting-briefing cover?

It supports deal reviews, board and committee sessions, vendor discussions, client meetings, regulatory reviews, and dispute strategy sessions.

Does meeting-briefing provide legal advice?

No. It assists with legal prep workflows and information gathering, but all briefings must be reviewed by team members for accuracy.

Source text

SKILL.md · Apache-2.0
---
name: meeting-briefing
description: 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.
---

# 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

© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor