meeting-briefing

anthropics/knowledge-work-plugins · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill meeting-briefing
0 commentsdiscussion
summary

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.

skill.md

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

After the meeting:

  1. Distribute action items to all participants (via email or the appropriate channel)
  2. Set calendar reminders for deadlines
  3. Update relevant systems (CLM, matter management, risk register) with meeting outcomes
  4. File meeting notes in the appropriate document repository
  5. Flag urgent items that need immediate attention

Tracking Cadence

  • High priority items: Check daily until completed
  • Medium priority items: Check at next team sync or weekly review
  • Low priority items: Check at next scheduled meeting or monthly review
  • Overdue items: Escalate to the owner and their manager; flag in next relevant meeting
how to use meeting-briefing

How to use meeting-briefing on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add meeting-briefing
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill meeting-briefing

The skills CLI fetches meeting-briefing from GitHub repository anthropics/knowledge-work-plugins and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/meeting-briefing

Reload or restart Cursor to activate meeting-briefing. Access the skill through slash commands (e.g., /meeting-briefing) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.646 reviews
  • Kiara Liu· Dec 20, 2024

    meeting-briefing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Alexander Yang· Dec 20, 2024

    I recommend meeting-briefing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Charlotte Perez· Dec 20, 2024

    meeting-briefing reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Shikha Mishra· Dec 8, 2024

    We added meeting-briefing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 27, 2024

    Useful defaults in meeting-briefing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Chen Rahman· Nov 11, 2024

    meeting-briefing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Fatima Abbas· Nov 11, 2024

    Registry listing for meeting-briefing matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Neel Verma· Nov 3, 2024

    meeting-briefing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Layla Gill· Oct 22, 2024

    meeting-briefing has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Pratham Ware· Oct 18, 2024

    Registry listing for meeting-briefing matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 46

1 / 5