agentleFS
nisarthnisarth/claude-skills-store/skills/legal/meeting-briefing/SKILL.md

meeting-briefing

Skill1 starsChanged 7 months agoMITView on GitHub

Prepare structured briefings for meetings with legal relevance. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context and action tracking are needed. Trigger with "meeting briefing", "prep me for the meeting", "board meeting prep", "negotiation prep", or "compliance review prep".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always include authority limits so participants know what they can agree to.

    line 90
  2. Distinctive:

    After the meeting, update with captured action items, owners, and deadlines.

    line 93

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Legal Meeting Briefing

Prepare comprehensive meeting briefings with background research, key issues, talking points, authority limits, and post-meeting action tracking.

Workflow

Step 1: Classify Meeting Type

  • Negotiation: Counterparty positions, fallback terms, walk-away points, BATNA.
  • Board meeting: Governance matters, fiduciary considerations, required resolutions.
  • Compliance review: Audit findings, remediation progress, regulatory updates.
  • Litigation update: Case status, discovery timeline, settlement analysis, budget.
  • Deal review: Transaction structure, diligence findings, closing conditions.

Step 2: Gather Background

Prior meeting notes and action items, relevant contracts or filings, recent correspondence, internal authority limits, and external developments.

Step 3: Prepare Key Issues and Talking Points

For each agenda item: issue summary, our position, counterparty position (if applicable), risk areas, 2-3 talking points, and whether a decision is needed.

Step 4: Define Desired Outcomes

Specific agreements to reach, information to obtain, red lines, and fallback positions.

Output Format

## Meeting Briefing
**Meeting**: [Title] | **Date**: [YYYY-MM-DD HH:MM]
**Type**: [Negotiation / Board / Compliance / etc.]

### Attendees
| Name | Organization | Role | Notes |
|------|-------------|------|-------|

### Agenda and Briefing Notes
**Item 1: [Topic]**
- Our position: [What we want]
- Their position: [What they want]
- Risk: [If unresolved]
- Talking points: 1) [Point] 2) [Point]
- Decision needed: [Yes/No]

### Red Lines and Authority
- Do not agree to: [List]
- Authority to agree to: [List]
- Escalation: If [condition], consult [Name]

### Desired Outcomes
1. [Outcome]

Examples

User: "Prep me for tomorrow's contract negotiation with Acme Corp" Action: Pull the current MSA draft, identify open terms, map each party's position, prepare fallback positions for key commercial terms, and set red lines from the playbook.

User: "Board meeting briefing for the quarterly compliance update" Action: Compile compliance metrics, open audit findings with remediation status, regulatory developments, and items requiring board approval.

User: "Prepare a litigation update meeting brief for the patent case" Action: Summarize case status, recent filings, budget versus actual spend, settlement analysis, and strategic recommendations.

Best Practices

  • Distribute the briefing at least 24 hours before the meeting.
  • Always include authority limits so participants know what they can agree to.
  • For negotiations, prepare both ideal and acceptable fallback positions.
  • For board meetings, flag items requiring formal board action.
  • After the meeting, update with captured action items, owners, and deadlines.
  • Store completed briefings in the matter file for institutional memory.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.