Localized reading guide
meeting-briefingPurpose, usage and source
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.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
legal/skills/meeting-briefing/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- research
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
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.
How the upstream workflow works
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?
Upstream passage · L14 ↗Step 2: Assess Preparation Needs
Based on the meeting type, determine what preparation is needed:
Upstream passage · L23 ↗Step 3: Gather Context from Connected Sources
Pull relevant information from each connected source:
Upstream passage · L38 ↗## 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 |Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Meeting Briefing Skill
- Step 1: Identify the Meeting
- Step 2: Assess Preparation Needs
- Step 3: Gather Context from Connected Sources
- Calendar
- Chat (e.g., Slack, Teams)
- Documents (e.g., Box, Egnyte, SharePoint)
- CLM (if connected)
- CRM (if connected)
- Step 4: Synthesize into Briefing
- Step 5: Identify Preparation Gaps
- Deal Review Meetings
- Board and Committee Meetings
- Regulatory Meetings
- During/After the Meeting
- Action Item Best Practices
- Follow-Up
- Tracking Cadence
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
4d19bc2ddb2138d1b306b150c5d0900ce0a398d5ab690b8eba8101ef33d98baa