ME

Assists in preparing structured, legally-contextualized meeting briefings and tracking follow-up actions.

Install

mkdir -p .claude/skills/meeting-briefing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2059" && unzip -o skill.zip -d .claude/skills/meeting-briefing && rm skill.zip

Installs to .claude/skills/meeting-briefing

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
265 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Identify meeting types for legal prep
  • Extract key agenda topics and participants
  • Summarize legal risks for briefings
  • Track action items from meetings

How it works

Synthesizes provided context and background documentation into a structured brief template tailored for specific legal meeting archetypes.

Inputs & outputs

You give it
Meeting details or context description.
You get back
Structured briefing document with action items.

When to use meeting-briefing

  • Prepare for a vendor contract negotiation
  • Summarize legal risks for board meetings
  • Draft meeting agenda with regulatory topics
  • Track legal action items

About this skill

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

When not to use it

  • For providing binding legal advice
  • When the meeting has no legal or regulatory relevance

Prerequisites

Calendar integration (implied)Source documents

Limitations

  • No substitute for professional legal review
  • Requires manual verification of briefings
  • Dependent on quality of source context

How it compares

Provides a legal-specific preparation methodology rather than general meeting minute summaries.

Compared to similar skills

meeting-briefing side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
meeting-briefing (this skill)26moNo flagsIntermediate
notion-meeting-intelligence66moNo flagsIntermediate
resume-handoff36moNo flagsIntermediate
personal-assistant39moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

More by anthropics

View all by anthropics

frontend-design

anthropics

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

481544

pptx

anthropics

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

393763

webapp-testing

anthropics

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

353585

mcp-builder

anthropics

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

136215

skill-creator

anthropics

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.

128200

docx

anthropics

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

93225

You might also like

notion-meeting-intelligence

openai

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

656

resume-handoff

parcadei

Resume work from handoff document with context analysis and validation

333

personal-assistant

ailabs-393

This skill should be used whenever users request personal assistance tasks such as schedule management, task tracking, reminder setting, habit monitoring, productivity advice, time management, or any query requiring personalized responses based on user preferences and context. On first use, collects comprehensive user information including schedule, working habits, preferences, goals, and routines. Maintains an intelligent database that automatically organizes and prioritizes information, keeping relevant data and discarding outdated context.

36

digital-brain

muratcankoylan

This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.

15

meeting-sync

amanaiproduct

Sync new Granola meetings to local Knowledge folder. Use during morning planning, when user asks "what should I do today", or asks to review/sync meetings.

13

my-skill-name

dadbodgeoff

Brief description of what this skill does and when to use it. Be specific about capabilities and use cases to help agents decide when to load this skill.

12

Search skills

Search the agent skills registry