Meeting Briefing
Generate structured legal-team meeting briefings with context gathering and action-item tracking before negotiations, board sessions, or compliance reviews.
Overview
Meeting Briefing is an agent skill most often used in Build (also Validate, Ship) that prepares structured briefings and action tracking for meetings with legal relevance.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill meeting-briefingWhat is this skill?
- Five-step meeting prep methodology: identify meeting, assess prep needs, gather context, draft structured briefing, trac
- Meeting-type matrix covering deal review, board meeting, vendor call, team sync, client meeting, and regulatory discussi
- Explicit legal-workflow framing with accuracy review disclaimer—assists workflows without providing legal advice
- Tailors preparation to attendee roles, agenda, and the legal member’s role (advisor, presenter, observer, negotiator)
- Supports post-meeting action tracking for items with legal relevance
- 5-step meeting prep methodology
- 6 meeting types in the prep-needs matrix
Adoption & trust: 1.6k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a high-stakes meeting soon but scattered context, unclear attendee interests, and no consistent briefing format for legal or compliance topics.
Who is it for?
Small teams or solo operators juggling vendor negotiations, board prep, or compliance check-ins who want templated legal-adjacent meeting briefs.
Skip if: Users seeking definitive legal advice, automated contract redlines, or meetings with zero governance risk where a simple agenda suffices.
When should I use this skill?
Preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.
What do I get? / Deliverables
You receive a structured pre-meeting brief aligned to meeting type and role, plus a path to capture action items after the session—ready for human accuracy review.
- Structured meeting briefing document
- Action-item list tied to meeting outcomes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build/PM because the skill produces planning artifacts and role clarity before high-stakes meetings that unblock delivery and governance work. PM subphase covers stakeholder meetings, agendas, and follow-ups—the skill’s Step 1–2 methodology maps directly to meeting identification and prep-needs assessment.
Where it fits
Draft a negotiation brief before committing to vendor contract scope and open legal questions.
Prep a client or deal-review sync with attendee roles and a typed prep-needs checklist.
Structure background for a compliance or regulatory discussion before launch sign-off.
Turn post-incident or policy meetings into tracked action items for the next iteration cycle.
How it compares
Use instead of freeform chat summaries when you need meeting-type-specific prep tables and legal-workflow discipline.
Common Questions / FAQ
Who is meeting-briefing for?
In-house legal contributors, founders handling their own vendor or board conversations, and agents supporting knowledge-work plugins who need repeatable meeting prep.
When should I use meeting-briefing?
During Build/PM for deal and client syncs; in Validate when scoping contract negotiations; and in Ship when compliance or security review meetings need structured background before sign-off.
Is meeting-briefing safe to install?
Check the Security Audits panel on this page; treat outputs as drafts requiring human legal review and never as authoritative legal advice.
SKILL.md
READMESKILL.md - Meeting Briefing
# 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 ``` ## M