meeting-briefing-step-1-identify-the-meeting

Sub-skill of meeting-briefing: Step 1: Identify the Meeting (+4).

5 stars

Best use case

meeting-briefing-step-1-identify-the-meeting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of meeting-briefing: Step 1: Identify the Meeting (+4).

Teams using meeting-briefing-step-1-identify-the-meeting should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/step-1-identify-the-meeting/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/business/legal/meeting-briefing/step-1-identify-the-meeting/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/step-1-identify-the-meeting/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How meeting-briefing-step-1-identify-the-meeting Compares

Feature / Agentmeeting-briefing-step-1-identify-the-meetingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Sub-skill of meeting-briefing: Step 1: Identify the Meeting (+4).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Step 1: Identify the Meeting (+4)

## 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

Related Skills

teams-meeting-pipeline

5
from vamseeachanta/workspace-hub

Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.

daily-briefing

5
from vamseeachanta/workspace-hub

Provide sales professionals with a prioritized daily action plan and pipeline overview

meeting-briefing

5
from vamseeachanta/workspace-hub

Prepare structured briefings for meetings with legal relevance and track action items

hidden-folder-audit-step-1-inventory-all-hidden-folders

5
from vamseeachanta/workspace-hub

Sub-skill of hidden-folder-audit: Step 1: Inventory All Hidden Folders (+4).

discipline-refactor-how-to-identify-disciplines

5
from vamseeachanta/workspace-hub

Sub-skill of discipline-refactor: How to Identify Disciplines.

skill-creator-step-1-name

5
from vamseeachanta/workspace-hub

Skill-creator checklist template. Use when scaffolding a new skill with step-by-step instructions and verification items.

skill-creator-step-1-define-the-skill-scope

5
from vamseeachanta/workspace-hub

Define skill scope and write frontmatter. Use when creating a new skill to establish problem, inputs, outputs, and YAML metadata.

clean-code-step-1-api-compatibility-check-mandatory-before-wr

5
from vamseeachanta/workspace-hub

Sub-skill of clean-code: Step 1: API Compatibility Check (MANDATORY before writing shims) (+2).

nextflow-pipelines-step-3-run-test-profile

5
from vamseeachanta/workspace-hub

Sub-skill of nextflow-pipelines: Step 3: Run Test Profile.

nextflow-pipelines-step-2-select-pipeline

5
from vamseeachanta/workspace-hub

Sub-skill of nextflow-pipelines: Step 2: Select Pipeline.

nextflow-pipelines-step-0-acquire-data-geosra-only

5
from vamseeachanta/workspace-hub

Sub-skill of nextflow-pipelines: Step 0: Acquire Data (GEO/SRA Only).

orcaflex-monolithic-to-modular-step-1-convert-dat-yml

5
from vamseeachanta/workspace-hub

Sub-skill of orcaflex-monolithic-to-modular: Step 1: Convert .dat to .yml (if needed) (+4).