skills/meeting-briefing-anthropic/SKILL.md
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.
npx skillsauth add lawvable/awesome-legal-skills meeting-briefing-anthropicInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Determine the meeting context from the user's request or calendar:
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 |
Pull relevant information from each connected source:
Organize gathered information into a structured briefing (see template below).
Flag anything that could not be found or verified:
## 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]
Additional briefing sections:
Additional briefing sections:
Additional briefing sections:
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 |
After the meeting:
tools
Toolkit for comprehensive Spreadsheet reading, creation, editing, and analysis with visual quality control. Use to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing tabular data, (3) Modifying existing spreadsheets while preserving formulas, (4) Building financial models with proper formatting, (5) Data visualization with in-sheet charts, or any other spreadsheet tasks.
development
Professional Excel spreadsheet creation with a focus on aesthetics and data analysis. Use when creating spreadsheets for organizing, analyzing, and presenting structured data in a clear and professional format.
development
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
tools
Build VS Code extensions from scratch or convert existing JS/React/Vue apps. Supports commands, webviews (React/Vue), custom editors, tree views, and AI agent integration via file-bridge IPC. Use when user wants to create a VS Code extension, convert a web app to an extension, add webviews or custom UIs to VS Code, implement tree views, build custom file editors, integrate with AI agents, or package/publish extensions (.vsix).