meeting-briefing

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.

10,671 stars

Best use case

meeting-briefing 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 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

$curl -o ~/.claude/skills/meeting-briefing/SKILL.md --create-dirs "https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/legal/skills/meeting-briefing/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/meeting-briefing/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How meeting-briefing Compares

Feature / Agentmeeting-briefingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/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.

Related Guides

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

daily-briefing

10671
from anthropics/knowledge-work-plugins

Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".

pipeline-review

10671
from anthropics/knowledge-work-plugins

Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals.

forecast

10671
from anthropics/knowledge-work-plugins

Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.

draft-outreach

10671
from anthropics/knowledge-work-plugins

Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".

create-an-asset

10671
from anthropics/knowledge-work-plugins

Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.

competitive-intelligence

10671
from anthropics/knowledge-work-plugins

Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".

call-summary

10671
from anthropics/knowledge-work-plugins

Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.

update

10671
from anthropics/knowledge-work-plugins

Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

task-management

10671
from anthropics/knowledge-work-plugins

Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.

memory-management

10671
from anthropics/knowledge-work-plugins

Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.

write-spec

10671
from anthropics/knowledge-work-plugins

Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

synthesize-research

10671
from anthropics/knowledge-work-plugins

Synthesize user research from interviews, surveys, and feedback into structured insights. Use when you have a pile of interview notes, survey responses, or support tickets to make sense of, need to extract themes and rank findings by frequency and impact, or want to turn raw feedback into roadmap recommendations.