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.
Prepare structured briefings for meetings with legal relevance and track action items.
Install Legal Meeting Briefing
$ npx skills add borghei/Claude-Skills --skill legal-meeting-briefing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills legal-meeting-briefing --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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/legal/legal-meeting-briefing .claude/skills/legal-meeting-briefing && 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 "legal-meeting-briefing" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/legal-meeting-briefing into .claude/skills/legal-meeting-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-meeting-briefing", 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/borghei/Claude-Skills/tree/main/legal/legal-meeting-briefingType 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 borghei/Claude-Skills --skill legal-meeting-briefing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills legal-meeting-briefing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/legal/legal-meeting-briefing .agents/skills/legal-meeting-briefing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "legal-meeting-briefing" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/legal-meeting-briefing into .agents/skills/legal-meeting-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-meeting-briefing", 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 borghei/Claude-Skills --skill legal-meeting-briefing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills legal-meeting-briefing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/legal/legal-meeting-briefing .cursor/skills/legal-meeting-briefing && 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 "legal-meeting-briefing" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/legal-meeting-briefing into .cursor/skills/legal-meeting-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-meeting-briefing", 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/borghei/Claude-Skills.git --path legal/legal-meeting-briefing--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 borghei/Claude-Skills --skill legal-meeting-briefing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills legal-meeting-briefing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/legal/legal-meeting-briefing .gemini/skills/legal-meeting-briefing && 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 "legal-meeting-briefing" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/legal-meeting-briefing into .gemini/skills/legal-meeting-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-meeting-briefing", 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 borghei/Claude-Skills legal-meeting-briefingInstalls 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 borghei/Claude-Skills --skill legal-meeting-briefing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/legal/legal-meeting-briefing .github/skills/legal-meeting-briefing && 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 "legal-meeting-briefing" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/legal-meeting-briefing into .github/skills/legal-meeting-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-meeting-briefing", 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 borghei/Claude-Skills --skill legal-meeting-briefing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills legal-meeting-briefing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/legal/legal-meeting-briefing .opencode/skills/legal-meeting-briefing && 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 "legal-meeting-briefing" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/legal-meeting-briefing into .opencode/skills/legal-meeting-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-meeting-briefing", 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
legal-meeting-briefing- GitHub stars
- 891
- Token cost
- ~3.2k tokens
- SKILL.md length
- 1,041 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 354
- Repo updated
- First seen
- Licence
- MIT
At a glance
Prepare structured briefings for meetings with legal relevance and track action items.
- Works in 2 steps: Meeting Brief Generator… → Action Item Tracker…
- Prepping legal meetings
- SKILL.md covers Overview, Table of Contents, Clarify First and Tools, plus 8 more sections
- Runs Python scripts from its folder; calls python
What it does
Legal Meeting Briefing is an agent skill from borghei/Claude-Skills. Prepare structured briefings for meetings with legal relevance and track action items. Use when prepping legal meetings.
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/briefing_templates.md`, `references/meeting_type_guides.md` and `scripts/action_item_tracker.py`).
It sits in Productivity & Automation, covering Meeting notes and agendas. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Prepping legal meetings
- Tasks that involve Meeting notes and agendas
Example prompts
- “/legal-meeting-briefing”
Requirements
- Python 3
Workflow steps
2 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 4a698e8. 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
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
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
Legal Meeting Briefing loads about 3.2k tokens when it runs, and up to ~9.3k if it reads all its reference files. Until then it costs about 36 tokens; SKILL.md has 1,041 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); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,041 words, ~3,226 tokens.
Download SKILL.mdSave it as
.claude/skills/legal-meeting-briefing/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- legal-meeting-briefing
- description
- Prepare structured briefings for meetings with legal relevance and track action items. Use when prepping legal meetings.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.0
- metadata.author
- The Glass Room
- metadata.category
- legal
- metadata.domain
- legal-operations
- metadata.updated
- 2026-04-10
- metadata.tags
- meeting-briefing, legal-ops, action-items, preparation, meetings
⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.
Legal Meeting Briefing Skill
Overview
Production-ready toolkit for preparing structured briefings for meetings with legal relevance and tracking resulting action items. Supports 8 meeting types with type-specific preparation guidance, a 13-section briefing template, and action item management with priority levels and follow-up cadence. Designed for legal teams preparing counsel, in-house attorneys, and legal operations professionals for productive meetings.
Table of Contents
- Tools
- Reference Guides
- Workflows
- Meeting Types
- Troubleshooting
- Success Criteria
- Scope & Limitations
- Anti-Patterns
- Tool Reference
Clarify First
Before generating the briefing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Meeting type — deal-review, board, regulatory, litigation, etc. — selects which type-specific sections appear (e.g. privilege considerations only for regulatory/litigation)
- Participants with orgs and roles — populate the counterparty-dynamics and interests sections; without them the brief is generic
- Objective / agenda — sets the depth and which sections matter; drives the preparation-gap list
- Privilege sensitivity — for regulatory/government or litigation meetings, determines what goes in the privilege section vs what can be shared
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the briefing.
Tools
1. Meeting Brief Generator (scripts/meeting_brief_generator.py)
Generate a meeting briefing skeleton pre-populated with sections based on meeting type.
python scripts/meeting_brief_generator.py \
--type deal-review \
--title "Series B Term Sheet Review" \
--date 2026-04-15 \
--participants '[{"name":"Jane Smith","org":"Legal","role":"Lead Counsel"}]'
python scripts/meeting_brief_generator.py \
--type board \
--title "Q1 Board Meeting" \
--date 2026-04-20 \
--agenda "Legal update,Risk report,Pending approvals" --json
python scripts/meeting_brief_generator.py \
--type regulatory \
--title "FDA Pre-Submission Meeting" \
--date 2026-05-01 \
--participants '[{"name":"Dr. Lee","org":"FDA","role":"Reviewer"}]'2. Action Item Tracker (scripts/action_item_tracker.py)
Manage action items from legal meetings with priority levels, ownership, and status tracking.
python scripts/action_item_tracker.py add \
--title "Draft NDA for Vendor X" \
--owner "Jane Smith" \
--priority high \
--deadline 2026-04-20 \
--meeting "Series B Review"
python scripts/action_item_tracker.py list \
--filter-status open \
--filter-priority high
python scripts/action_item_tracker.py complete --id 3
python scripts/action_item_tracker.py dashboard --json
python scripts/action_item_tracker.py update --id 5 \
--status in-progress --notes "Waiting for counterparty response"Reference Guides
| Reference | Purpose |
|---|---|
references/meeting_type_guides.md | Preparation guidance for all 8 meeting types |
references/briefing_templates.md | Complete 13-section briefing template and action item tracking |
Workflows
5-Step Briefing Methodology
| Step | Action | Output |
|---|---|---|
| 1. Identify Meeting | Determine meeting type, participants, objectives | Meeting classification |
| 2. Assess Preparation Needs | Select type-specific sections and depth | Section checklist |
| 3. Gather Context | Collect documents, prior notes, open issues | Background materials |
| 4. Synthesize into Briefing | Run generator; populate sections with gathered context | Draft briefing |
| 5. Identify Preparation Gaps | Review for missing info; flag items needing follow-up | Gap list |
Meeting Type Selection
| Meeting Type | Key Indicator |
|---|---|
| Deal Review | Transaction under consideration or in progress |
| Board/Committee | Board of directors, audit committee, compensation committee |
| Vendor Call | Meeting with supplier, contractor, or service provider |
| Team Sync | Internal legal team meeting |
| Client/Customer | External client or customer-facing meeting |
| Regulatory/Government | Meeting with regulator, agency, or government body |
| Litigation/Dispute | Meeting about active or potential legal dispute |
| Cross-Functional | Meeting with stakeholders from multiple departments |
Action Item Workflow
- Capture -- Record action items during or immediately after meeting
- Assign -- Set owner, priority, and deadline for each item
- Track -- Monitor progress via dashboard; update status as work progresses
- Follow-Up -- Follow cadence based on priority level
- Close -- Mark complete when done; archive for audit trail
Follow-Up Cadence
| Priority | Follow-Up Frequency | Escalation |
|---|---|---|
| High | Daily check-in | Escalate after 2 missed days |
| Medium | Weekly check-in | Escalate after 1 missed week |
| Low | Monthly check-in | Escalate after 1 missed month |
| Overdue | Immediate escalation | Notify supervisor and meeting owner |
Meeting Types
Deal Review
Focus: Transaction analysis, contract review, approval requirements.
| Section | Content |
|---|---|
| Deal Summary | Parties, structure, value, timeline |
| Contract Status | Draft version, open issues, redline items |
| Approval Requirements | Who must approve; delegated authority limits |
| Counterparty Dynamics | Negotiation position, prior dealings, leverage |
| Comparable Deals | Similar transactions for benchmarking terms |
Board/Committee
Focus: Legal department update, risk highlights, governance.
| Section | Content |
|---|---|
| Legal Department Update | Headcount, budget, key accomplishments |
| Risk Highlights | Top legal risks with likelihood and impact |
| Regulatory Update | Recent regulatory changes affecting the organization |
| Pending Approvals | Items requiring board or committee action |
| Litigation Summary | Active matters, reserves, settlement status |
Show full SKILL.md (439 more words)Show less
Regulatory/Government
Focus: Compliance posture, enforcement patterns, privilege considerations.
| Section | Content |
|---|---|
| Regulatory Body Context | Agency structure, jurisdiction, enforcement priorities |
| Enforcement Patterns | Recent enforcement actions in the sector |
| Matter History | Prior interactions, submissions, correspondence |
| Privilege Considerations | What is privileged; what can be shared |
| Compliance Posture | Current compliance status; remediation progress |
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Brief missing type-specific sections | Wrong meeting type selected | Review meeting type descriptions; select the most specific type |
| Participants not formatted | JSON format error | Use valid JSON array: '[{"name":"X","org":"Y","role":"Z"}]' |
| Action items not persisting | Tracker uses file-based storage | Ensure write permissions in working directory; check action_items.json |
| Dashboard shows stale data | Cached data from previous run | Re-run dashboard command; items are loaded fresh from storage |
| Overdue items not flagged | Clock/timezone mismatch | Verify system date; deadlines use YYYY-MM-DD format |
| Agenda items not populating | Comma-separated format expected | Use --agenda "Item 1,Item 2,Item 3" format |
| Brief too generic | Minimal parameters provided | Add participants, agenda, and type-specific context |
| Action item ID not found | Item was completed or deleted | Run list --filter-status all to see all items including completed |
Success Criteria
- Preparation Coverage: Every legal meeting has a briefing covering all relevant sections for its type
- Action Item Capture: 100% of action items captured with owner, deadline, and priority within 24 hours
- On-Time Completion: 90%+ of action items completed by deadline
- Meeting Effectiveness: Participants report improved preparation and productivity (measured by survey)
- Follow-Up Compliance: High-priority items followed up daily; medium weekly; low monthly
Scope & Limitations
This skill covers:
- Meeting briefing generation with type-specific sections for 8 meeting types
- Action item tracking with CRUD operations, filtering, and status dashboard
- Follow-up cadence management based on priority levels
- Preparation gap identification for pre-meeting readiness
This skill does NOT cover:
- Calendar integration or meeting scheduling
- Real-time meeting notes or transcription
- Email drafting or distribution of briefings
- Document management or version control for meeting materials
- Video conferencing or collaboration tool integration
Anti-Patterns
| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Generic briefing for all meeting types | Misses type-specific concerns; wastes prep time on irrelevant sections | Select correct meeting type; use type-specific guidance |
| Capturing action items days after meeting | Details forgotten; ownership unclear; deadlines slip | Capture during meeting or within 2 hours; use tracker immediately |
| Single owner for all items | Creates bottleneck; no accountability for individual tasks | Assign specific owner per item; each item has exactly one owner |
| No follow-up on action items | Items go stale; commitments missed; trust erodes | Follow cadence: high=daily, medium=weekly, low=monthly |
| Skipping privilege considerations for regulatory meetings | Inadvertent privilege waiver; disclosed protected communications | Always complete privilege section for regulatory/government meetings |
Tool Reference
scripts/meeting_brief_generator.py
Generate meeting briefing skeleton from parameters.
usage: meeting_brief_generator.py [-h] [--json]
--type {deal-review,board,vendor,team-sync,
client,regulatory,litigation,cross-functional}
--title TITLE
--date DATE
[--participants PARTICIPANTS]
[--agenda AGENDA]
[--output OUTPUT]
options:
-h, --help Show help message and exit
--json Output in JSON format
--type Meeting type (determines sections included)
--title Meeting title
--date Meeting date (YYYY-MM-DD)
--participants JSON array of participants: [{"name","org","role","interests"}]
--agenda Comma-separated agenda items
--output Write briefing to file instead of stdoutscripts/action_item_tracker.py
Manage action items with CRUD operations and status dashboard.
usage: action_item_tracker.py [-h] [--json]
{add,list,update,complete,dashboard} ...
commands:
add Add a new action item
list List action items with optional filters
update Update an existing action item
complete Mark an action item as complete
dashboard Show action item summary dashboard
add options:
--title TITLE Action item description (required)
--owner OWNER Responsible person (required)
--priority {high,medium,low} Priority level (required)
--deadline DEADLINE Due date YYYY-MM-DD (required)
--meeting MEETING Source meeting name
--notes NOTES Additional notes
list options:
--filter-status {open,in-progress,complete,overdue,all}
--filter-priority {high,medium,low,all}
--filter-owner OWNER
update options:
--id ID Action item ID (required)
--status {open,in-progress,complete}
--priority {high,medium,low}
--deadline DEADLINE
--notes NOTES
complete options:
--id ID Action item ID (required)
dashboard options:
(no additional options)© borghei, MIT. 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 4 other files (scripts, references) in legal/legal-meeting-briefing of borghei/Claude-Skills.
- SKILL.md
- references/briefing_templates.md
- references/meeting_type_guides.md
- scripts/action_item_tracker.py
- scripts/meeting_brief_generator.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Legal Meeting Briefing 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 |
|---|---|---|---|---|---|---|
| Legal Meeting Briefing this skillborghei/Claude-Skills | 891 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Meeting Notesoutline/outline | 41k | — | ~551 | Automated safety check: Pass | Custom licence | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| Challenge Baseline ModelAgibotTech/genie_sim | 1.4k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Handwriting Stand Uplimin112/min-skill | 454 | — | ~2.5k | Automated safety check: Pass | None | |
| Daily Journalravila4/claude-adhd-skills | 158 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
Challenge Baseline Model
AgibotTech/genie_sim
Provision and launch the Simulation Challenge baseline inference model end to end: clone the inference code from a given git repo/branch, download the checkpoints from ModelScope into the repo's…
Handwriting Stand Up
limin112/min-skill
Turn a screen recording of handwriting (or a photo of handwritten text) into a single-file HTML "continuation" — the recording plays, the ink lifts off the page as solid 3D letters, a short animated…
Daily Journal
ravila4/claude-adhd-skills
Draft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills.
Granola
ArtemXTech/claude-code-obsidian-starter
Query and sync Granola meetings to Obsidian vault. An agent skill from ArtemXTech/claude-code-obsidian-starter.
More from borghei/Claude-Skills
All 354 skills in this repoAgent Harness
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
Agents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Related
Categories
Questions about Legal Meeting Briefing
What does Legal Meeting Briefing do?
Prepare structured briefings for meetings with legal relevance and track action items. Legal Meeting Briefing is an agent skill from borghei/Claude-Skills. Prepare structured briefings for meetings with legal relevance and track action items.
When should I use Legal Meeting Briefing?
Legal Meeting Briefing fits situations like: prepping legal meetings; tasks that involve Meeting notes and agendas.
How do I install Legal Meeting Briefing in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill legal-meeting-briefing -a claude-code`. Or copy the skill folder (legal/legal-meeting-briefing in borghei/Claude-Skills) into .claude/skills/legal-meeting-briefing in your project. Claude Code loads it when a task matches its description.
How do I install Legal Meeting Briefing in Codex?
Run `npx skills add borghei/Claude-Skills --skill legal-meeting-briefing -a codex`. Or copy the skill folder (legal/legal-meeting-briefing in borghei/Claude-Skills) into .agents/skills/legal-meeting-briefing in your project. Codex loads it when a task matches its description.
Can I use Legal Meeting Briefing 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 borghei/Claude-Skills --skill legal-meeting-briefing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/legal-meeting-briefing, .gemini/skills/legal-meeting-briefing, .github/skills/legal-meeting-briefing and .opencode/skills/legal-meeting-briefing in your project.
What does Legal Meeting Briefing need to run?
Going by SKILL.md and its folder, Legal Meeting Briefing needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Legal Meeting Briefing 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 Legal Meeting Briefing 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Legal Meeting Briefing use?
Legal Meeting Briefing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Legal Meeting Briefing use?
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.1k tokens, read only when the agent opens those files.
What are the alternatives to Legal Meeting Briefing?
Skills that share tags, products or a category with Legal Meeting Briefing: Meeting Notes (outline/outline, 41k stars), Management Talk (thananon/9arm-skills, 3.2k stars), Challenge Baseline Model (AgibotTech/genie_sim, 1.4k stars) and Handwriting Stand Up (limin112/min-skill, 454 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Legal Meeting Briefing?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 891 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.