meeting-briefing-anthropic
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.
What this skill does
# 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 ``` ## 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 Af
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.