AI驱动的会议智能助手 — 自动转录、摘要、提取行动项、生成后续跟进并追踪决策,覆盖您的会议...
AI 会见情报专家是一项面向实际任务的技能,主要用于将混乱的会议转变为结构化、 可行的见解;这个AI 授权的会议情报助理处理整个会议周期。
从功能定位来看,该技能强调把分散的操作要求整理成清晰、可复用的处理流程,使用户能够围绕既定目标快速准备输入、选择执行方式并获得结构化结果。实际使用前应先确认任务范围、数据来源、运行环境、必要权限和关键参数,再依据技能说明逐步执行;
若输入条件不完整,应先补齐信息或采用保守配置,避免因错误假设导致结果偏离需求。执行过程中需要关注工具调用是否成功、接口或依赖是否可用、输出格式是否符合预期,并对异常提示、缺失字段和边界情况进行处理;涉及批量任务时,还应保存进度,避免中断后重复操作。
将混乱无序的会议转化为结构清晰、可执行的洞见。这款由 AI 驱动的会议智能助手覆盖完整的会议生命周期——从议程准备到决策追踪——让您得以专注于真正重要的事情:会议对话本身。
会议纪要、智能会议、会议分析、会议摘要、提取行动项、会议转录、开会被忘meeting notes, meeting summary, transcribe meeting, action items, decision tracking, prepare meeting, meeting agenda1. INPUT: 会议转录文本 / 会议笔记 / 原始文本 ↓ 2. PROCESS: AI 提取关键信息 - 发言人及其角色 - 讨论主题 - 已做决策 - 已分配的行动项 - 提出的问题 ↓ 3. OUTPUT: 结构化的会议智能输出 - 执行摘要 - 行动项清单 - 决策日志 - 后续跟进建议
阶段 1:准备阶段 ├── 接收会议主题/上下文 ├── 生成议程模板 ├── 拉取相关背景数据 └── 准备参会人简报材料 阶段 2:会议进行中 ├── 实时记录会议笔记 ├── 标记关键节点 ├── 对照议程追踪时间使用情况 └── 记录未决事项 阶段 3:会后处理 ├── 转录并整理会议笔记 ├── 生成多版本摘要 ├── 提取行动项 ├── 起草后续跟进内容 └── 更新各类追踪器 阶段 4:跟进落实 ├── 向参会人发送摘要 ├── 创建任务提醒 ├── 追踪行动项状态 └── 标记超期未处理项
Meeting: Q2 Product Planning Date: 2026-05-15 Attendees: Sarah (PM), Mike (Eng), Lisa (Design), John (Sales) Notes: - Sarah opened with Q1 review, metrics looking good - Mike mentioned technical blockers on API integration - Lisa showed new mockups, everyone loved the dark mode - John said enterprise clients are asking for SSO - Decided to prioritize SSO for next sprint - Mike will create technical spec by Friday - Lisa to update mockups with SSO flows by next week - Sarah to schedule follow-up with enterprise team
预期输出:
## Meeting Summary: Q2 Product Planning ### Quick Take (30 sec) Q1 metrics positive. Team aligned on Q2 priorities: SSO feature for enterprise clients. Technical spec due Friday, mockups by next week. ### Decisions Made 1. Prioritize SSO implementation in next sprint 2. Enterprise team meeting to be scheduled ### Action Items | Item | Owner | Due Date | |------|-------|----------| | Create technical spec for SSO | Mike | 2026-05-20 | | Update mockups with SSO flows | Lisa | 2026-05-22 | | Schedule enterprise team follow-up | Sarah | 2026-05-18 | ### Discussion Highlights - Enterprise clients requesting SSO (high priority) - Dark mode mockups well received - API integration blockers acknowledged
输入:原始会议转录文本或要点式笔记
输出:结构化行动项列表,包含:
输入:“与工程和产品团队举行的季度规划会议”
输出:
## Q2 Planning Meeting Agenda ### Pre-Meeting (15 min) - Review Q1 OKRs and completion status - Prepare Q2 targets draft ### Agenda (60 min total) 1. Q1 Retrospective (15 min) - Wins to celebrate - Areas for improvement 2. Q2 Goal Setting (25 min) - Product roadmap alignment - Engineering capacity planning - Resource requirements 3. Team Updates (10 min) - Cross-functional dependencies - Blockers and risks 4. Wrap-Up (10 min) - Confirm decisions - Assign next steps
## [Meeting Title] **Date:** [Date] **Time:** [Start] - [End] **Location:** [Room/Video Link] **Attendees:** [Names and Roles] ### Executive Summary [2-3 sentence overview] ### Agenda vs. Actual | Topic | Planned | Actual | |-------|---------|--------| | ... | ... | ... | ### Key Decisions 1. [Decision 1] 2. [Decision 2] ### Action Items - [ ] [Task] - @Owner - Due: [Date] - [ ] [Task] - @Owner - Due: [Date] ### Open Questions - [Question 1] - [Question 2] ### Next Meeting - Scheduled: [Date/Time] - Focus: [Topics]
Subject: [Meeting Title] - Key Decisions & Your Action Items Hi [Name], Following up on today's [meeting name]. Here's a quick summary: **What We Decided:** - [Decision 1] - [Decision 2] **Your Next Steps:** - [Action item 1] - by [date] - [Action item 2] - by [date] **Resources:** - [Link to meeting notes] - [Link to relevant documents] Let me know if you have any questions! Best, [Your name]
| 使用场景 | 推荐工具 |
|---|---|
| 日历同步 | Google Calendar, Outlook |
| 笔记记录 | Notion, Obsidian, Evernote |
| 任务管理 | Todoist, Asana, Linear, Jira |
| 视频会议 | Zoom, Google Meet, Teams |
| CRM 同步 | Salesforce, HubSpot |
| 邮件跟进 | Gmail, Outlook |
解决方案:向 AI 提供您手头已有的任何内容——要点罗列、片段式转录,甚至语音备忘录。本助手可处理碎片化输入,并将明确标示各项信息的置信度水平。
解决方案:启用每日汇总(daily digest)功能,获取当日全部会议概览,交叉比对行动项,并识别潜在的日程冲突。
解决方案:当归属关系模糊时,请标记该条目待确认,而非随意指派;添加 “Verify owner” 标签以便后续澄清。
解决方案:强调敏感会议应在本地环境处理。提供 “sanitize” 模式,在保留整体结构的前提下自动脱敏敏感姓名与公司名称。
相关专题
热门下载
相关下载
精品课程
共6课时 | 54.7万人学习
共89课时 | 134万人学习
共49课时 | 82.5万人学习