Import: Meeting Briefing (Anthropic)
What it does
This import adapter migrates a meeting-briefing skill originally authored for Anthropic's Claude API into the mini-claude-for-legal standard format. Legal and deal teams routinely prepare structured briefing documents before client meetings, negotiation sessions, regulatory hearings, and board presentations. A meeting-briefing skill automates the preparation: given inputs about the meeting, it generates a concise, well-structured brief that tells every participant what they need to know before walking into the room.
The Anthropic-native version may have used a system prompt for meeting prep, a calendar-integration hook, or a document-analysis pipeline feeding into a briefing template. This adapter normalises all of those shapes.
Import config
| Field |
Source mapping |
Default if absent |
meeting_type |
Legacy type |
negotiation_session |
participant_profiling |
Legacy profiles boolean |
true |
agenda_parsing |
Legacy parse_agenda boolean |
true |
document_inputs |
Legacy docs array |
None (optional) |
key_issues_limit |
Legacy max_issues |
5 |
action_tracking |
Legacy action_items boolean |
true |
output_length |
Legacy length |
concise (max 2 pages equivalent) |
language |
Legacy lang |
en |
Dry-run preview
IMPORT PREVIEW — meeting-briefing-anthropic
Source shape : Anthropic meeting-briefing system prompt
Meeting type : negotiation_session (default)
Participant profiles: enabled
Agenda parsing : enabled
Key issues : max 5
Action tracking : enabled
Output length : concise (2-page equivalent)
Briefing structure (post-import)
1. Meeting overview
- Purpose and expected outcome
- Date, time, forum (virtual / in-person / hybrid)
- Governing confidentiality constraints (e.g. legal privilege, NDA in place)
2. Participants
| Name |
Role |
Organisation |
Known position / interests |
Watch-outs |
| [name] |
[role] |
[org] |
[known stance] |
[sensitivities] |
3. Agenda items
For each item:
- Background (1–2 sentences)
- Our position / objective
- Likely counterparty position
- Decision to be made / outcome sought
4. Key documents
- List any contracts, term sheets, or regulatory materials being discussed; with one-line status note.
5. Key issues (max 5)
The most important substantive issues, ranked by priority. Each issue: background → our position → counterparty position → risk if unresolved.
6. Action items (pre-meeting)
What must be done before the meeting: approvals needed, information to obtain, positions to confirm.
7. Post-meeting action-item template
Pre-formatted table for capturing decisions and owners during or after the meeting.
Legal-context specifics
- Privilege: if the meeting involves legal advice, mark the brief "Privileged and Confidential — Attorney-Client Communication" (common law) or equivalent (civil law: secret professionnel).
- Regulatory hearings: for meetings with regulators (DFSA, CBUAE, ACPR, FCA), adapt the participant-profiling section to include the regulator's known supervisory priorities and any outstanding examination findings.
- Negotiation sessions: link to the relevant
import-legal-simulation-patrick-munro or import-mediation-dispute-analysis-jinzhe-tan output if a dispute is being negotiated.
- Arabic language: for meetings with UAE government counterparts or MENA clients, add a brief Arabic-language summary block.
Failure modes
| Error |
Likely cause |
Resolution |
agenda_empty |
No agenda provided by user |
Generate placeholder agenda from meeting type; flag as draft |
participants_unknown |
No participant list |
Prompt user; generate blank participant table |
output_too_long |
Legacy prompt produced verbose output |
Enforce output_length: concise override |
privilege_not_marked |
Legal briefing lacks privilege header |
Auto-prepend privilege header if meeting involves legal advice |
Related skills
- [[import-contract-review-anthropic]]
- [[import-nda-triage-anthropic]]
- [[import-vendor-due-diligence-patrick-munro]]
- [[import-legal-simulation-patrick-munro]]
- [[ops-meeting-prep]]
1---2name: import-meeting-briefing-anthropic3description: Use when migrating a meeting-briefing skill originally built for the Anthropic Claude API into the mini-claude-for-legal format. The adapter maps legacy meeting-preparation logic — agenda analysis, participant profiling, key-issue summaries, and action-item tracking — into the standard skill model for use in legal and deal-team contexts.4license: MIT5metadata:6 id: import.meeting-briefing-anthropic7 category: import8 jurisdictions: [__multi__]9 priority: P310 intent: [__import__, meeting-briefing, legal-ops, migration, anthropic]11 related: [import-contract-review-anthropic, import-nda-triage-anthropic, import-vendor-due-diligence-patrick-munro, ops-meeting-prep]12 source: https://skillmd.com/skills/sboghossian-mini-claude-for-legal/import-meeting-briefing-anthropic13 upstream: Louis — HAQQ Legal AI (github.com/sboghossian/mini-claude-for-legal)14 version: "1.0"15---1617# Import: Meeting Briefing (Anthropic)1819## What it does2021This import adapter migrates a **meeting-briefing skill** originally authored for Anthropic's Claude API into the `mini-claude-for-legal` standard format. Legal and deal teams routinely prepare structured briefing documents before client meetings, negotiation sessions, regulatory hearings, and board presentations. A meeting-briefing skill automates the preparation: given inputs about the meeting, it generates a concise, well-structured brief that tells every participant what they need to know before walking into the room.2223The Anthropic-native version may have used a system prompt for meeting prep, a calendar-integration hook, or a document-analysis pipeline feeding into a briefing template. This adapter normalises all of those shapes.2425## Import config2627| Field | Source mapping | Default if absent |28|---|---|---|29| `meeting_type` | Legacy `type` | `negotiation_session` |30| `participant_profiling` | Legacy `profiles` boolean | `true` |31| `agenda_parsing` | Legacy `parse_agenda` boolean | `true` |32| `document_inputs` | Legacy `docs` array | None (optional) |33| `key_issues_limit` | Legacy `max_issues` | `5` |34| `action_tracking` | Legacy `action_items` boolean | `true` |35| `output_length` | Legacy `length` | `concise` (max 2 pages equivalent) |36| `language` | Legacy `lang` | `en` |3738## Dry-run preview3940```41IMPORT PREVIEW — meeting-briefing-anthropic42Source shape : Anthropic meeting-briefing system prompt43Meeting type : negotiation_session (default)44Participant profiles: enabled45Agenda parsing : enabled46Key issues : max 547Action tracking : enabled48Output length : concise (2-page equivalent)49```5051## Briefing structure (post-import)5253### 1. Meeting overview54- Purpose and expected outcome55- Date, time, forum (virtual / in-person / hybrid)56- Governing confidentiality constraints (e.g. legal privilege, NDA in place)5758### 2. Participants59| Name | Role | Organisation | Known position / interests | Watch-outs |60|---|---|---|---|---|61| [name] | [role] | [org] | [known stance] | [sensitivities] |6263### 3. Agenda items64For each item:65- Background (1–2 sentences)66- Our position / objective67- Likely counterparty position68- Decision to be made / outcome sought6970### 4. Key documents71- List any contracts, term sheets, or regulatory materials being discussed; with one-line status note.7273### 5. Key issues (max 5)74The most important substantive issues, ranked by priority. Each issue: background → our position → counterparty position → risk if unresolved.7576### 6. Action items (pre-meeting)77What must be done before the meeting: approvals needed, information to obtain, positions to confirm.7879### 7. Post-meeting action-item template80Pre-formatted table for capturing decisions and owners during or after the meeting.8182## Legal-context specifics8384- **Privilege**: if the meeting involves legal advice, mark the brief "Privileged and Confidential — Attorney-Client Communication" (common law) or equivalent (civil law: secret professionnel).85- **Regulatory hearings**: for meetings with regulators (DFSA, CBUAE, ACPR, FCA), adapt the participant-profiling section to include the regulator's known supervisory priorities and any outstanding examination findings.86- **Negotiation sessions**: link to the relevant `import-legal-simulation-patrick-munro` or `import-mediation-dispute-analysis-jinzhe-tan` output if a dispute is being negotiated.87- **Arabic language**: for meetings with UAE government counterparts or MENA clients, add a brief Arabic-language summary block.8889## Failure modes9091| Error | Likely cause | Resolution |92|---|---|---|93| `agenda_empty` | No agenda provided by user | Generate placeholder agenda from meeting type; flag as draft |94| `participants_unknown` | No participant list | Prompt user; generate blank participant table |95| `output_too_long` | Legacy prompt produced verbose output | Enforce `output_length: concise` override |96| `privilege_not_marked` | Legal briefing lacks privilege header | Auto-prepend privilege header if meeting involves legal advice |9798## Related skills99100- [[import-contract-review-anthropic]]101- [[import-nda-triage-anthropic]]102- [[import-vendor-due-diligence-patrick-munro]]103- [[import-legal-simulation-patrick-munro]]104- [[ops-meeting-prep]]