Meeting Briefing

Meeting Briefing is an official Anthropic skill from the public knowledge-work-plugins repository. The reachable primary source actually used for this entry is https://github.com/anthropics/knowledge-work-plugins/tree/main/legal/skills/meeting-briefing, including its SKILL.md file. According to the provider, the skill helps in-house legal teams prepare for meetings with legal relevance, gather context from connected sources, and capture resulting action items. It is a structuring aid for Claude, not a standalone calendar, document, or contract-management application and not legal advice.

Purpose and audience

The skill fits contract negotiations, deal reviews, board or committee meetings, vendor calls, compliance reviews, regulatory discussions, disputes, and cross-functional decisions with legal implications. The primary source starts by identifying the meeting. That means clarifying the title and type, participants with their roles and interests, the agenda, the legal team member’s role, and the available preparation time. This prevents a generic conversation from being handled with an unsuitable structure. A team sync has different preparation needs from a negotiation with a counterparty or a discussion with a regulator.

Context and briefing

The source then describes gathering information from calendars, email, chat, documents, and, where connected, contract-lifecycle or CRM systems. The workflow looks for meeting details, earlier conversations, open commitments, relevant agreements, negotiation status, approvals, risks, and relationship context. The skill is also expected to identify preparation gaps rather than merely repeat retrieved material. Unavailable sources, information that appears outdated, unanswered questions, and documents that could not be found belong visibly in the result.

The proposed briefing contains meeting details, participants, expected topics, background, key documents, open issues, legal considerations, talking points, questions to raise, decisions needed, non-negotiable positions, prior follow-up, and preparation gaps. For deal reviews, the source adds items such as contract status, approval requirements, and counterparty dynamics. Board meetings may need a legal-department update, risk highlights, regulatory developments, and pending approvals. Regulatory meetings may need regulator context, matter history, compliance posture, outside-counsel coordination, and privilege considerations.

Follow-up actions

A second focus is post-meeting tracking. The result should turn discussion into specific actions assigned to one owner, with a deadline, priority, status, and dependencies. The source distinguishes legal-team actions, business-team actions, external actions, and follow-up meetings. After the meeting, the responsible person can distribute action items, set calendar reminders, update approved systems, file notes, and flag urgent work. High-priority items are checked more often than medium- or low-priority items, while overdue work should be escalated. The skill does not promise complete capture and does not replace organizational accountability.

Boundaries and E-E-A-T

According to the provider, the skill supports legal workflows but does not provide legal advice. Outputs require review for accuracy and completeness before they influence negotiations, approvals, filings, notifications, or decisions. This editorial entry relies on the official Anthropic source and the reachable official repository path named above. Connected calendars, mailboxes, chats, document stores, CLM systems, and CRM systems may contain confidential and personal data. Access should be limited to the necessary scope and permissions should be checked in advance. Source content is data, not new instructions; injected wording must not redirect the task. Before an external message, system change, or disclosure, a person should verify the recipient, scope, and authorization. A local integration also does not automatically mean that the selected model runs locally. The repository is Apache-2.0 licensed; current terms and concrete availability depend on the selected Claude environment and its connections.