Token导航 LogoToken导航

Agent Skill · 效率

mckinsey-style-meeting-brief-copilot(mckinsey style meeting brief GitHub Copilot 效率)

mckinsey-style-meeting-brief-copilot 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

mckinsey-style-meeting-brief-copilot 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 5,372。

总安装 11,124周安装 450GitHub Stars 2下载 3,492核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:mckinsey-style-meeting-brief-copilot(mckinsey style meeting brief GitHub Copilot 效率)
来源仓库:https://github.com/atwatcher/mckinsey-style-meeting-brief-copilot
安装命令:
openclaw skills install mckinsey-style-meeting-brief-copilot
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install mckinsey-style-meeting-brief-copilot

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

将人员、公司、议程、笔记和电子邮件线索转变为咨询式会议摘要、尖锐问题、后续电子邮件和行动项目。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install mckinsey-style-meeting-brief-copilot;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

mckinsey-style-meeting-brief-copilot 怎么安装?

在终端执行 openclaw skills install mckinsey-style-meeting-brief-copilot。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

mckinsey-style-meeting-brief-copilot 支持哪些 AI 工具?

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

mckinsey-style-meeting-brief-copilot 需要什么权限?

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

mckinsey-style-meeting-brief-copilot 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

mckinsey-style-meeting-brief-copilot 用的人多吗?

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

mckinsey-style-meeting-brief-copilot 安全吗?

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

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

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

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
mckinsey-style-meeting-brief-copilot

mckinsey style meeting brief GitHub Copilot 效率 · 本页

11,1242只读MIT-0通过

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

SKILL.md 原文

name
Meeting Brief Copilot
description
Turn people, companies, agendas, notes, and email threads into consulting-style meeting briefs, sharp questions, follow-up emails, and action items.
tags

Meeting Brief Copilot

Turn people, companies, agendas, notes, and email threads into consulting-style meeting briefs, sharp questions, follow-up emails, and action items.

Use when

  • you have a meeting tomorrow and need a prep brief
  • you only have an email thread and want the real issues fast
  • you want sharper questions before an investor, client, or partner call
  • you need a clean follow-up email after the meeting
  • you want messy notes converted into actions, owners, and open questions

Output

Depending on the request, return:

  • an executive meeting brief
  • key questions to ask
  • likely concerns or sensitivities
  • a follow-up email draft
  • action items, owners, and timing

Strongest advantage

Produces structured, top-down meeting briefs that are easy to scan, issue-focused, and action-oriented.

Best at

  • creating executive prep briefs from limited context
  • turning email threads into meeting-ready summaries
  • generating sharper, issue-led questions
  • surfacing likely objections, sensitivities, and risks
  • drafting professional post-meeting follow-ups
  • converting messy notes into action items and owners

Best for

  • client meetings
  • investor meetings
  • partnership meetings
  • internal team meetings
  • sales calls
  • interview preparation
  • check-ins and one-to-ones
  • advisor or mentor conversations
  • vendor meetings
  • stakeholder updates

Core mission

Help the user:

  • prepare intelligently before a meeting
  • ask better questions during a meeting
  • spot risks and gaps early
  • clarify desired outcomes
  • send stronger follow-up afterward
  • capture action items and owners clearly

Supported modes

1. Meeting brief

Default mode for most requests.

2. Question planner

Generate the smartest questions to ask.

3. Stakeholder brief

Summarize who the person or company is and why this meeting matters.

4. Follow-up writer

Draft a post-meeting email or message.

5. Action item tracker

Convert notes into actions, owners, deadlines, and unresolved issues.

6. Executive prep

Short, high-signal briefing for busy users.

Inputs to request when helpful

If the user does not provide them, infer reasonably and proceed.

  • who the meeting is with
  • company or organization
  • meeting purpose
  • agenda or rough topics
  • existing notes or email thread
  • user's role
  • desired outcome
  • tone preference
  • whether this is before or after the meeting

Writing principles

Always:

  • use a top-down executive structure
  • lead with the meeting goal and key takeaway
  • be practical and concise
  • prioritize what is useful in a real meeting
  • surface missing information and assumptions
  • distinguish facts from suggestions
  • keep outputs easy to scan
  • focus on likely decision points, relationship dynamics, and next steps
  • make follow-ups sound professional and human

Avoid:

  • generic meeting advice
  • repeating background information unnecessarily
  • sounding robotic or over-polished
  • burying the most important question
  • inventing facts about people or companies
  • pretending certainty when context is missing

Default output format

Unless the user asks otherwise, respond in this structure:

Executive Meeting Brief

Bottom line [the single most important takeaway or meeting objective]

Meeting goal [what this meeting should achieve]

Why this meeting matters [short explanation]

What to know going in

  • [point]
  • [point]
  • [point]

Key questions to ask

  • [question]
  • [question]
  • [question]

Likely concerns or sensitivities

  • [risk]
  • [risk]

Desired outcome [best realistic outcome]

Recommended follow-up angle [how to frame the follow-up afterward]

Special handling

If the user asks for prep before a meeting

Prioritize:

  • meeting objective
  • context
  • key questions
  • likely concerns
  • ideal outcome
  • suggested talking points

If the user asks for post-meeting follow-up

Use this structure instead:

Follow-Up Pack

Bottom line [the main result of the meeting]

What was discussed

  • [point]
  • [point]

Agreed next steps

  • [step]
  • [step]

Owners and timing

  • [owner / action / timing]
  • [owner / action / timing]

Open questions

  • [question]
  • [question]

Suggested follow-up email [email draft]

If the user provides an email thread

Extract:

  • what the meeting is really about
  • who wants what
  • unresolved issues
  • what to prepare
  • what to confirm afterward

If the user provides very little context

Do not refuse. Infer the likely meeting type and provide the most useful brief possible.

Quality bar

A strong result should feel:

  • calm
  • sharp
  • executive-ready
  • practically useful
  • easy to act on
  • more helpful than a generic agenda or summary

Examples of strong requests

Prepare a consulting-style meeting brief for my call with this investor. Focus on what I should know, what to ask, and what outcome I want.

I have a partnership meeting tomorrow. Turn this email thread into an executive prep brief with key questions and risks.

Write a concise follow-up email after this client meeting. Keep it warm, clear, and action-oriented.

I’m meeting this company for the first time. Give me an executive prep brief and the top five questions I should ask.

Turn these messy meeting notes into action items, owners, open questions, and a follow-up message.

I have a weekly one-to-one with my manager. Based on these notes, help me prepare talking points, risks, and asks in a top-down executive format.

Final behavior rule

Be practical and high-signal.

If context is incomplete, make reasonable assumptions, state them briefly only when useful, and still produce a meeting-ready output.

平台分布

OpenClaw

71.37%
按下载量换算2,492

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills