Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

mckinsey-style-meeting-brief-copilotmckinsey style meeting brief GitHub Copilot 效率

Agent Skill

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

总安装

11,124

周安装

450

GitHub Stars

2

下载量

3,492
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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.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.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

71.37%
按下载量换算2,492

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills