ElasticFlow
Legal Pluginby Anthropic✓

When a board meeting or vendor call is on the calendar, /meeting-briefing pulls context from email, CLM, and CRM into a structured prep doc.

Runs on
ChatGPTChatGPTClaudeClaudeGeminiGeminiOpenClawOpenClaw

Prepare board, deal, and vendor meeting briefings and track action items.

  • Meeting types: deal review, board, vendor call, team sync, regulatory, litigation, cross-functional
  • Sources: calendar, email, chat (Slack/Teams), Box/Egnyte/SharePoint, CLM, CRM
  • Briefing template: participants, agenda, background, open issues, talking points, red lines
  • Action item tracker: single owner, specific deadline, priority, dependency notes
  • Privilege flags for regulatory and litigation meetings

Who this is for

General Counsel

Walk into board meetings, deal reviews, and regulatory calls with full context pulled from email, CLM, and CRM

See skills for this role
Corporate Counsel

Prep for cross-functional meetings by pulling the right context without 90 minutes of digging

See skills for this role

What it does

Board meeting tomorrow, you have 2 hours to prep

/meeting-briefing pulls the legal department update, top risks from the register, regulatory developments since last quarter, and pending board approvals — organized into the standard board template so you walk in ready.

Deal review for a $10M MSA negotiation

/meeting-briefing assembles contract status, open issues, counterparty's likely positions from email history, comparable deals, and approval requirements — with a red lines section for what cannot be conceded.

Quarterly vendor business review with 6 stakeholders

/meeting-briefing pulls agreement status, performance metrics, prior call notes, and the open issues table — plus a participants table mapping each attendee's role and key interests.

Action item triage after the all-hands strategy meeting

/meeting-briefing captures the 12 action items from your notes, assigns single owners with specific deadlines, distinguishes legal/business/external categories, and sets calendar reminders by priority cadence.

How it works

1

Identify the meeting: title, type, participants, your role, prep time available

2

Skill scans connected sources for relevant context (last 3 months)

3

Synthesizes into the structured briefing template

4

Flags preparation gaps and missing information

5

Captures action items after the meeting with owner, deadline, and tracking cadence

Example

Your meeting
Board meeting tomorrow 9am. I'm presenting the legal department Q1 update.
Meeting brief — 12 minutes
Meeting Details
Board Meeting Q1 2026
Date: 2026-04-09 9:00-11:00 AM ET
Location: HQ Boardroom + Zoom
Your Role: Presenter (legal department update, 15 min slot)
Legal Department Update
Matters opened Q1: 47 (vs 39 Q4)
Matters closed Q1: 41
Wins: TechCorp settlement ($2.3M favorable), DPA enforcement closed without action
New matters: 2 employment claims, 1 IP dispute, 4 vendor disputes
Top Risks
RED 18: TechCorp follow-on IP claim (new since Q4)
ORANGE 12: GDPR enforcement risk on EU data transfers (unchanged)
ORANGE 10: Open employment class action exposure (decreased from RED 16)
Pending Board Approvals
1. Authorization to settle TechCorp — recommended approval
2. Outside counsel budget increase ($400K) — needs vote
3. Updated D&O insurance terms — informational
Talking Points
Lead with TechCorp win narrative
Frame Q1 matter increase as economic conditions, not legal failure
Flag GDPR transfer risk as the one item to watch in Q2

Metrics this improves

Board Prep Time
Board update assembled from email/CLM/risk register in 15 minutes instead of 3 hours of digging
Legal
Legal as Business Enabler
Legal becomes the prepared participant in every cross-functional meeting
Legal
Strategic vs Reactive Work
Walk into meetings with full context instead of being caught off-guard
Legal

Works with

Gmail
manual

Searches recent correspondence about meeting topic and participants

Google Calendar
manual

Pulls meeting details, attendees, and prior meetings with same participants

Salesforce
manual

Pulls account/opportunity context for client and customer meetings

Slack
manual

Surfaces team discussions about the meeting topic from connected channels

Microsoft Teams
manual

Pulls Teams chat context about meeting topic and participants

Outlook
manual

Pulls calendar context and recent email threads with meeting participants

Ironclad
manual

Pulls relevant contract status for deal review and vendor meetings

iManage
manual

Pulls relevant memos, prior briefings, and draft materials from iManage

Part of
9 skills

Legal Plugin

by Anthropic

/meeting-briefing is one of 9 skills in this plugin.

See all 9 skills
⚖ Compare side-by-side
Compare with 3 similar skills
In the same department: Legal (13 skills total)
Compare →

Similar skills

Auto-suggested by attribute overlap. Side-by-side comparison shows what differs.

Compare all 4 →

E-Signature Routing

by Anthropic✓
↳USvsUS, EU +1(Jurisdictions)·textvsfile-upload, text(What you provide)·markdownvsmarkdown, pdf(Output formats)

NDA triage

by Anthropic✓
↳USvsUS, EU +1(Jurisdictions)·textvsfile-upload, text(What you provide)·producevsdecide(Type of work)

Vendor status

by Anthropic✓
↳USvsUS, EU(Jurisdictions)·textvstext, tool-access(What you provide)·producevsanalyze(Type of work)
Sorted by attribute overlap × differentiation. Meeting Briefing shares 14+ attributes with each.
View on GitHub

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 context: meeting title and type (deal review, board, vendor call, team sync, client, regulatory, litigation, cross-functional), participants and their roles/interests, agenda, your role (advisor/presenter/observer/negotiator), preparation time available.

Step 2: Assess Preparation Needs by Meeting Type

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

  • Calendar: meeting details, prior meetings with same participants (last 3 months), related/follow-up meetings, time constraints
  • Email: recent correspondence, prior follow-up threads, open action items, relevant documents shared
  • Chat (Slack/Teams): recent discussions, messages from/about participants, team discussions about related matters
  • Documents (Box/Egnyte/SharePoint): agendas, prior notes, relevant agreements/memos/briefings, draft materials
  • CLM: relevant contracts with counterparty, status and open negotiation items, approval workflow status, amendment/renewal history
  • CRM: account/opportunity info, relationship history, deal stage, stakeholder map

Step 4: Synthesize into Briefing

Use template (see below).

Step 5: Identify Preparation Gaps

Flag what could not be found or verified.

Briefing Template

## Meeting Brief

### Meeting Details
- Meeting, Date/Time, Duration, Location, Your Role

### Participants
| Name | Organization | Role | Key Interests | Notes |

### Agenda / Expected Topics

### Background and Context
[2-3 paragraph summary]

### Key Documents

### Open Issues
| Issue | Status | Owner | Priority | Notes |

### Legal Considerations

### Talking Points

### Questions to Raise

### Decisions Needed

### Red Lines / Non-Negotiables (if negotiation)

### Prior Meeting Follow-Up

### Preparation Gaps

Meeting-Type Specific Guidance

Deal Review Meetings

Additional sections: deal summary (parties, value, structure, timeline), contract status, approval requirements, counterparty dynamics, comparable deals.

Board and Committee Meetings

Additional sections: legal department update, risk highlights with changes, regulatory update, pending approvals/resolutions, litigation summary.

Regulatory Meetings

Additional sections: regulatory body context (priorities, enforcement patterns), matter history, compliance posture, counsel coordination, privilege considerations.

Action Item Tracking

| # | Action Item | Owner | Deadline | Priority | Status |

Best Practices

  • Be specific: "Send redline of Section 4.2" not "Follow up on contract"
  • Single owner: each action item has exactly one owner
  • Specific deadline: not "soon" or "ASAP"
  • Note dependencies: if action depends on another action or external input
  • Distinguish types: legal team / business team / external / follow-up meetings

Follow-Up After Meeting

  1. Distribute action items to participants
  2. Set calendar reminders for deadlines
  3. Update relevant systems (CLM, matter management, risk register)
  4. File meeting notes
  5. Flag urgent items

Tracking Cadence

  • High priority: daily until completed
  • Medium: at next team sync or weekly review
  • Low: at next scheduled meeting or monthly review
  • Overdue: escalate to owner and manager