Meeting Copilot

v1.0.3

会议运营 Copilot — 支持会前 briefing 生成、会中结构化纪要整理、会后待办追踪与 follow-up 草稿。面向需要系统性管理会议全生命周期的职场人士。提供 boss mode(向上汇报视角)和 executor mode(向下追踪视角)两种输出格式。⚠️ 不提供实时语音转录、日历集成或自动提醒。

0· 132·0 current·0 all-time
byhaidong@harrylabsj

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for harrylabsj/meeting-copilot.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Meeting Copilot" (harrylabsj/meeting-copilot) from ClawHub.
Skill page: https://clawhub.ai/harrylabsj/meeting-copilot
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install meeting-copilot

ClawHub CLI

Package manager switcher

npx clawhub@latest install meeting-copilot
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (meeting briefing / minutes / follow-up) align with the packaged code and SKILL.md. The code implements parsing, action-item extraction and draft generation that match the documented inputs/outputs. There are no unrelated required binaries, env vars, or config paths.
Instruction Scope
SKILL.md limits behavior to transforming user-provided meeting text into structured outputs and explicitly states it will not access calendars, do real-time transcription, or send mail. The handler.py helpers operate only on provided arguments/strings (parsing, regex, formatting) and do not reference external endpoints or unexpected system files.
Install Mechanism
No install specification or external downloads are present; this is an instruction + code bundle (no install hooks), so nothing is written to disk beyond running the provided handler if invoked. This is the lowest-risk install profile.
Credentials
The skill declares no required environment variables, credentials, or config paths and the code does not read os.environ or other secrets. No disproportionate credential requests are present.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system settings. It runs as an ordinary handler module with an optional self-test entry point — normal behavior for an instruction-only skill with tests.
Assessment
This skill appears coherent and limited to transforming user-supplied meeting text into briefings, minutes, and follow-up drafts. Before installing or using it with sensitive meetings, consider: (1) There is no network or calendar integration — you'll need to paste meeting content manually. (2) Do not paste confidential material into third-party or shared agents unless you trust their data handling. (3) Run the included tests locally (python3 tests/test_handler.py) to verify behavior in your environment. (4) Note there is no homepage or publisher metadata beyond the package files — if provenance matters for your organization, ask the provider for source hosting or additional author information.

Like a lobster shell, security has layers — review code before you run it.

latestvk978t2p7asy4eywfq7zv9wtd7h84dsz0
132downloads
0stars
4versions
Updated 2w ago
v1.0.3
MIT-0

Meeting Ops Copilot

会议全生命周期辅助,覆盖:会前 briefing → 会中纪要结构化整理 → 会后待办追踪与 follow-up 草稿。支持 boss / executor 两种模式输出。

Overview

本 skill 帮助用户系统性管理会议全生命周期:

  • 会前:基于议程和背景生成 briefing 材料,供主持或主讲人快速进入状态
  • 会中:将散乱的讨论内容整理为结构化纪要(讨论要点 / 决议 / 待办含负责人)
  • 会后:从纪要中提取待办清单和 follow-up 草稿邮件/消息

⚠️ 免责声明:本工具不提供实时语音转录、不接入日历、不发送通知。其输出依赖用户输入的原始信息,质量受限于输入完整性。

When to Use This Skill

  • 需要在会议前快速准备 briefing
  • 会议中或会议后需要整理出结构化纪要
  • 需要从纪要中生成待办追踪列表
  • 需要向老板(boss mode)或下属(executor mode)发送 follow-up 邮件/消息草稿

Workflow

Mode 1: boss mode(向上汇报视角)

输出重点:结论先行、决策清晰、风险可见。

输入:会议主题 + 议程 + 背景要点(或原始讨论文本)
↓ 识别关键决议、支撑理由、潜在风险
↓ 输出:Boss-friendly Briefing(结论 + 要点 + 风险 + 建议行动)

Mode 2: executor mode(向下追踪视角)

输出重点:任务明确、责任到人、时间清楚。

输入:会议纪要 / 讨论要点 / 决议
↓ 提取待办事项(含负责人 / 截止 / 优先级)
↓ 输出:结构化待办列表 + follow-up 草稿

Input

字段类型必填说明
taskstring任务类型:briefing / minutes / followup
meeting_topicstring会议主题
meeting_datestring会议日期 YYYY-MM-DD
modestringbossexecutor
agendastring条件必填议程要点,多条用 | 分隔(briefing 必填)
raw_textstring条件必填原始讨论文本(minutes 必填)
decisionsstring可选已决事项,多条用 | 分隔
participantsstring可选参与者列表,多人用 | 分隔

Output

briefing(boss mode)

{
  "status": "success",
  "task": "briefing",
  "mode": "boss",
  "meeting_topic": "...",
  "meeting_date": "...",
  "sections": {
    "conclusion": "一句话结论",
    "key_points": ["要点1", "要点2"],
    "decisions_needed": ["待决策事项"],
    "risks": ["风险1", "风险2"],
    "suggested_actions": ["建议行动1"]
  },
  "briefing_text": "格式化 briefing 文本"
}

minutes(executor mode)

{
  "status": "success",
  "task": "minutes",
  "mode": "executor",
  "meeting_topic": "...",
  "meeting_date": "...",
  "minutes": {
    "discussion_points": ["讨论点1", "讨论点2"],
    "decisions": ["决议1"],
    "action_items": [
      {"task": "任务描述", "owner": "负责人", "deadline": "YYYY-MM-DD", "priority": "high|medium|low"}
    ]
  },
  "minutes_text": "格式化纪要文本"
}

followup

{
  "status": "success",
  "task": "followup",
  "mode": "boss|executor",
  "meeting_topic": "...",
  "followup_items": [...],
  "draft_email": "邮件草稿文本",
  "draft_message": "简短消息草稿"
}

Safety & Disclaimer

  • ⚠️ 本 skill 不接入日历系统,不发送通知,不进行实时语音转录
  • ⚠️ 输出的完整性和准确性依赖用户输入的原始信息,不做信息真实性担保
  • ⚠️ 本工具是辅助参考,不替代专业会议记录人员或法律/合规审查
  • 如涉及重大决策,请结合实际情况自行判断或咨询专业人士

Constraints

  • ❌ 不提供实时语音转录
  • ❌ 不接入日历(Google Calendar、钉钉日历等)
  • ❌ 不自动发送通知或邮件(仅生成草稿)
  • ❌ 不做会议录音存储

Examples

会前 Briefing(boss mode)

输入

task: briefing
meeting_topic: Q2 产品规划评审
meeting_date: 2026-04-05
mode: boss
agenda: Q2目标对齐|技术方案选型|资源评估
participants: 产品经理|研发负责人|设计负责人

输出:Boss-friendly briefing,包含结论先行的核心要点 + 风险 + 建议行动。

会中纪要整理(executor mode)

输入

task: minutes
meeting_topic: 周例会
meeting_date: 2026-03-31
mode: executor
raw_text: 讨论了A功能延期的风险;决定启用备选方案;张三分头对接供应商;李四负责测试
decisions: 启用备选方案
participants: 张三|李四|王五

输出:结构化纪要 + 提取的待办(含负责人)。

会后 Follow-up(executor mode)

输入

task: followup
meeting_topic: 周例会
mode: executor
decisions: 启用备选方案
(action_items from minutes output)

输出:待办追踪列表 + 邮件/消息草稿。

Acceptance Criteria

  • 支持 briefing / minutes / followup 三种 task
  • 支持 boss / executor 两种 mode
  • briefing 输出包含 conclusion / key_points / risks / suggested_actions
  • minutes 输出包含 discussion_points / decisions / action_items(含 owner/deadline/priority)
  • followup 输出包含结构化待办列表 + 邮件草稿 + 消息草稿
  • handler.py 带 if __name__ == "__main__": 自测分支,直接 python3 handler.py 可跑
  • skill.json / .claw/identity.json / tests/test_handler.py 齐全
  • 免责声明完整呈现于输出和文档中

Comments

Loading comments...