Vendor Due Diligence
borghei/Claude-Skills
Assess IT vendors and third-party partners with multi-factor risk scoring and regulatory compliance checklists.
Prepare structured briefings for meetings with legal relevance and track resulting action items.
Install Meeting Briefing Anthropic
$ npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lawve-ai/awesome-legal-skills meeting-briefing-anthropic --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/meeting-briefing-preparator-anthropic .claude/skills/meeting-briefing-anthropic && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "meeting-briefing-anthropic" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/meeting-briefing-preparator-anthropic into .claude/skills/meeting-briefing-anthropic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-briefing-anthropic", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/meeting-briefing-preparator-anthropicType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lawve-ai/awesome-legal-skills meeting-briefing-anthropic --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/meeting-briefing-preparator-anthropic .agents/skills/meeting-briefing-anthropic && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "meeting-briefing-anthropic" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/meeting-briefing-preparator-anthropic into .agents/skills/meeting-briefing-anthropic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-briefing-anthropic", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lawve-ai/awesome-legal-skills meeting-briefing-anthropic --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/meeting-briefing-preparator-anthropic .cursor/skills/meeting-briefing-anthropic && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "meeting-briefing-anthropic" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/meeting-briefing-preparator-anthropic into .cursor/skills/meeting-briefing-anthropic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-briefing-anthropic", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/lawve-ai/awesome-legal-skills.git --path skills/meeting-briefing-preparator-anthropic--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lawve-ai/awesome-legal-skills meeting-briefing-anthropic --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/meeting-briefing-preparator-anthropic .gemini/skills/meeting-briefing-anthropic && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "meeting-briefing-anthropic" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/meeting-briefing-preparator-anthropic into .gemini/skills/meeting-briefing-anthropic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-briefing-anthropic", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install lawve-ai/awesome-legal-skills meeting-briefing-anthropicInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/meeting-briefing-preparator-anthropic .github/skills/meeting-briefing-anthropic && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "meeting-briefing-anthropic" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/meeting-briefing-preparator-anthropic into .github/skills/meeting-briefing-anthropic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-briefing-anthropic", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lawve-ai/awesome-legal-skills meeting-briefing-anthropic --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/meeting-briefing-preparator-anthropic .opencode/skills/meeting-briefing-anthropic && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "meeting-briefing-anthropic" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/meeting-briefing-preparator-anthropic into .opencode/skills/meeting-briefing-anthropic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-briefing-anthropic", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
meeting-briefing-anthropic- GitHub stars
- 847
- Used in
- 1 other repo
- Token cost
- ~2.3k tokens
- SKILL.md length
- 839 words
- Files
- 3
- Skills in repo
- 154
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Prepare structured briefings for meetings with legal relevance and track resulting action items.
- Works in 5 steps: Identify the Meeting → Assess Preparation Needs → Gather Context from Connected Sources → …
- Preparing for contract negotiations
- SKILL.md covers Meeting Prep Methodology, Briefing Template, Meeting-Type Specific Guidance and Action Item Tracking
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Meeting Briefing Anthropic is an agent skill from lawve-ai/awesome-legal-skills. 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.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md`).
It sits in Productivity & Automation, covering Meeting notes and agendas, Regulatory compliance and Vendor and procurement management. The repository describes itself as: A curated list of awesome Agent Skills for automating legal work. The licence is Apache-2.0.
When your agent uses it
- Preparing for contract negotiations
- Compliance reviews
- Any meeting where legal context
- Background research
Example prompts
- “/meeting-briefing-anthropic”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 045f738. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Meeting Briefing Anthropic loads about 2.3k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 839 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from lawve-ai/awesome-legal-skills at commit 045f738, republished under its Apache-2.0 licence (© lawve-ai). 839 words, ~2,269 tokens.
Download SKILL.mdSave it as
.claude/skills/meeting-briefing-anthropic/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- meeting-briefing-anthropic
- description
- 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.
- metadata.author
- Anthropic
- metadata.license
- Apache-2.0
- metadata.version
- 2026.01.30
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
- 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)
Show full SKILL.md (327 more words)Show less
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:
- Distribute action items to all participants (via email or the appropriate channel)
- Set calendar reminders for deadlines
- Update relevant systems (CLM, matter management, risk register) with meeting outcomes
- File meeting notes in the appropriate document repository
- 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
© lawve-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in skills/meeting-briefing-preparator-anthropic of lawve-ai/awesome-legal-skills.
- SKILL.md
- LICENSE.txt
- README.md
Open the folder on GitHubat commit 045f738
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in lawve-ai/awesome-legal-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Meeting Briefing Anthropic next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Meeting Briefing Anthropic this skilllawve-ai/awesome-legal-skills | 847 | 1 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Vendor Due Diligenceborghei/Claude-Skills | 891 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Books And RecordsJoelLewis/finance_skills | 206 | — | ~11k | Automated safety check: Pass | MIT | |
| Rfp Response Compliance Reviewpnp/sharepoint-skills | 133 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Call Agent Commitment TrackerCALLE-AI/awesome-phone-call-agents | 107 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Procurement Auditvixues/LeAgent | 232 | — | ~321 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Books And Records
JoelLewis/finance_skills
Guide the design and maintenance of recordkeeping programs under SEC Rules 17a-3, 17a-4, and 204-2.
Rfp Response Compliance Review
pnp/sharepoint-skills
Reviews a draft proposal against the firm's configurable compliance rules — prohibited language, required disclosures, role and positioning boundaries, and procurement-submission requirements.
Call Agent Commitment Tracker
CALLE-AI/awesome-phone-call-agents
Offline heuristic CALL-E phone call transcript skill that extracts and classifies agent Commissive Speech Acts — promises, follow-up pledges, and delegation statements — into WITHDEADLINE…
Procurement Audit
vixues/LeAgent
Review procurement contracts and purchase packages against uploaded compliance rules (招标/采购制度).
Meeting Notes
outline/outline
Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.
More from lawve-ai/awesome-legal-skills
All 154 skills in this repoCustoms Trade Law Onur Kafkas
lawve-ai/awesome-legal-skills
U.S. An agent skill from lawve-ai/awesome-legal-skills.
Eu Data Act Oliver Schmidt Prietz
lawve-ai/awesome-legal-skills
Practitioner skill for advising on EU Regulation 2023/2854 (Data Act).
Litigation Deadline Calendar
lawve-ai/awesome-legal-skills
Calendar litigation and arbitration deadlines from a scheduling order.
Outlook Emails Lawvable
lawve-ai/awesome-legal-skills
Read, search, and download emails and attachments from Microsoft Outlook via OAuth2.
Ambiguity Report
lawve-ai/awesome-legal-skills
Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable.
Az Eu Website Privacy Audit
lawve-ai/awesome-legal-skills
Audits a website for compliance with Azerbaijan's Law on Personal Data No.
Related
Questions about Meeting Briefing Anthropic
What does Meeting Briefing Anthropic do?
Prepare structured briefings for meetings with legal relevance and track resulting action items. Meeting Briefing Anthropic is an agent skill from lawve-ai/awesome-legal-skills. Prepare structured briefings for meetings with legal relevance and track resulting action items.
When should I use Meeting Briefing Anthropic?
Meeting Briefing Anthropic fits situations like: preparing for contract negotiations; compliance reviews; any meeting where legal context; background research.
How do I install Meeting Briefing Anthropic in Claude Code?
Run `npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a claude-code`. Or copy the skill folder (skills/meeting-briefing-preparator-anthropic in lawve-ai/awesome-legal-skills) into .claude/skills/meeting-briefing-anthropic in your project. Claude Code loads it when a task matches its description.
How do I install Meeting Briefing Anthropic in Codex?
Run `npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a codex`. Or copy the skill folder (skills/meeting-briefing-preparator-anthropic in lawve-ai/awesome-legal-skills) into .agents/skills/meeting-briefing-anthropic in your project. Codex loads it when a task matches its description.
Can I use Meeting Briefing Anthropic in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lawve-ai/awesome-legal-skills --skill meeting-briefing-anthropic -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meeting-briefing-anthropic, .gemini/skills/meeting-briefing-anthropic, .github/skills/meeting-briefing-anthropic and .opencode/skills/meeting-briefing-anthropic in your project.
What does Meeting Briefing Anthropic need to run?
SKILL.md names no scripts, command-line tools or credentials: Meeting Briefing Anthropic is instructions for the agent only.
Does Meeting Briefing Anthropic access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Meeting Briefing Anthropic safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Meeting Briefing Anthropic use?
Meeting Briefing Anthropic is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Meeting Briefing Anthropic use?
About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Meeting Briefing Anthropic?
Skills that share tags, products or a category with Meeting Briefing Anthropic: Vendor Due Diligence (borghei/Claude-Skills, 891 stars), Books And Records (JoelLewis/finance_skills, 206 stars), Rfp Response Compliance Review (pnp/sharepoint-skills, 133 stars) and Call Agent Commitment Tracker (CALLE-AI/awesome-phone-call-agents, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Meeting Briefing Anthropic?
lawve-ai (a GitHub organization) maintains it in lawve-ai/awesome-legal-skills, which has 847 GitHub stars. The repository holds 154 skills in this directory. The repository was last updated on October 2, 2026.
Source: lawve-ai/awesome-legal-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.