Token导航 LogoToken导航

Agent Skill · 研究检索

meeting-briefing(会议简报)

meeting-briefing 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

meeting-briefing 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 5,756。

总安装 24,480周安装 993GitHub Stars 11,673下载 7,840核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:meeting-briefing(会议简报)
来源仓库:https://github.com/anthropics/knowledge-work-plugins
仓库路径:skills/meeting-briefing
安装命令:
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill meeting-briefing
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill meeting-briefing

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

meeting-briefing 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。它支持通过关键词或任务场景进行信息检索,帮助用户在海量数据中快速筛选出相关结果。

可通过 npx skills add 命令从 GitHub 仓库安装,具体用法建议参考原始 README 文件。安装前请确认权限范围和维护状态,注意可能涉及联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/meeting-briefing

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/anthropics/knowledge-work-plugins --skill meet…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

meeting-briefing 怎么安装?

在终端执行 npx skills add https://github.com/anthropics/knowledge-work-plugins --skill meeting-briefi…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

meeting-briefing 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

meeting-briefing 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

meeting-briefing 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

meeting-briefing 用的人多吗?

公开数据是累计安装 24,480 次,近一周安装 993 次,下载 7,840 次,GitHub 11,673 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

meeting-briefing 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 11,673 星,维护活跃度相对可查。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
meeting-briefing

会议简报 · 本页

24,48011,673只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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 TypeKey Prep Needs
Deal ReviewContract status, open issues, counterparty history, negotiation strategy, approval requirements
Board / CommitteeLegal updates, risk register highlights, pending matters, regulatory developments, resolution drafts
Vendor CallAgreement status, open issues, performance metrics, relationship history, negotiation objectives
Team SyncWorkload status, priority matters, resource needs, upcoming deadlines
Client / CustomerAgreement terms, support history, open issues, relationship context
Regulatory / GovernmentMatter background, compliance status, prior communications, counsel briefing
Litigation / DisputeCase status, recent developments, strategy, settlement parameters
Cross-FunctionalLegal 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

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)

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:

  1. Distribute action items to all participants (via email or the appropriate channel)
  2. Set calendar reminders for deadlines
  3. Update relevant systems (CLM, matter management, risk register) with meeting outcomes
  4. File meeting notes in the appropriate document repository
  5. 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

平台分布

Codex

39.17%
按下载量换算3,071

Claude

29.67%
按下载量换算2,326

Cursor

19.24%
按下载量换算1,508

Gemini CLI

8.9%
按下载量换算698

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills