{"id":"ca58f2f4-97fd-4b18-b010-e0f0051db047","entityType":"agent","slug":"clawhub-gechengling-ai-meeting-intelligence","name":"AI Meeting Intelligence Expert","canonicalUrl":"https://www.xpersona.co/agent/clawhub-gechengling-ai-meeting-intelligence","canonicalPath":"/agent/clawhub-gechengling-ai-meeting-intelligence","generatedAt":"2026-10-13T01:46:28.354Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T21:41:35.501Z","emptyReason":null},"description":"AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, and distributed teams who need to capture and act on meeting insights without manual note-taking. Keywords: meeting notes, meeting transcription, action items extraction, meeting summary, decision tracking, calendar integration, agenda preparation, meeting efficiency, AI meeting assistant, 会议纪要, 会议转录, 智能摘要, 行动项提取, 会议效率, 待办跟进, 决策追踪. Skill: AI Meeting Intelligence Expert Owner: gechengling Summary: AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams,","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 989 downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17ewqc4f2s6gpcbm88hy7fgvn85kg1g:ai-meeting-intelligence","sourceUrl":"https://clawhub.ai/gechengling/ai-meeting-intelligence","homepage":"https://clawhub.ai/gechengling/skills/ai-meeting-intelligence","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/gechengling/ai-meeting-intelligence","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/gechengling/skills/ai-meeting-intelligence","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meet"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:41:35.501Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:41:35.501Z","emptyReason":null},"stars":null,"forks":null,"downloads":989,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.0.2","tractionLabel":"989 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:41:35.487Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T21:41:35.501Z","lastCrawledAt":"2026-10-11T21:41:35.487Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T21:41:35.487Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.2","createdAt":"2026-09-28T05:21:16.580Z","changelog":"收窄触发：关键词改为必要不充分条件+必需上下文+六行非触发对照表+范围声明（SQP-1 中英双语）；会议类型表新增建议AI参与度列；合规表新增AI内容标识行；三个模块各补第二例；新增Example 6范围外请求路由；合规动态更新至2026-09-28","fileCount":3,"zipByteSize":14388},{"version":"1.0.1","createdAt":"2026-09-10T05:28:48.864Z","changelog":"1.0.1: 新增数据处理与隐私前置声明(数据最小化+保存确认门禁)、四模块各补实例、会议类型模板对照表、集成表扩至6列、示例4-5、生态与合规(截至2026-09-10)","fileCount":3,"zipByteSize":12215},{"version":"1.0.0","createdAt":"2026-05-19T12:06:28.281Z","changelog":"- Initial release of AI Meeting Intelligence Expert. - Automatically transcribes, summarizes, and extracts action items and decisions from meetings. - Supports multi-language transcription, speaker identification, and sentiment analysis. - Integrates with popular calendar, email, CRM, and task management tools. - Provides agenda generation, follow-up email drafts, and meeting analytics for improved efficiency and tracking.","fileCount":3,"zipByteSize":5561}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17ewqc4f2s6gpcbm88hy7fgvn85kg1g:ai-meeting-intelligence","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-13T01:46:28.353Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gechengling-ai-meeting-intelligence/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T21:41:35.501Z","emptyReason":null},"readme":"Skill: AI Meeting Intelligence Expert\n\nOwner: gechengling\n\nSummary: AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, and distributed teams who need to capture and act on meeting insights without manual note-taking. Keywords: meeting notes, meeting transcription, action items extraction, meeting summary, decision tracking, calendar integration, agenda preparation, meeting efficiency, AI meeting assistant, 会议纪要, 会议转录, 智能摘要, 行动项提取, 会议效率, 待办跟进, 决策追踪.\n\nTags: ai-meeting-intelligence:1.0.2, latest:1.0.2\n\nVersion history:\n\nv1.0.2 | 2026-09-28T05:21:16.580Z | user\n\n收窄触发：关键词改为必要不充分条件+必需上下文+六行非触发对照表+范围声明（SQP-1 中英双语）；会议类型表新增建议AI参与度列；合规表新增AI内容标识行；三个模块各补第二例；新增Example 6范围外请求路由；合规动态更新至2026-09-28\n\nv1.0.1 | 2026-09-10T05:28:48.864Z | user\n\n1.0.1: 新增数据处理与隐私前置声明(数据最小化+保存确认门禁)、四模块各补实例、会议类型模板对照表、集成表扩至6列、示例4-5、生态与合规(截至2026-09-10)\n\nv1.0.0 | 2026-05-19T12:06:28.281Z | auto\n\n- Initial release of AI Meeting Intelligence Expert.\n- Automatically transcribes, summarizes, and extracts action items and decisions from meetings.\n- Supports multi-language transcription, speaker identification, and sentiment analysis.\n- Integrates with popular calendar, email, CRM, and task management tools.\n- Provides agenda generation, follow-up email drafts, and meeting analytics for improved efficiency and tracking.\n\nArchive index:\n\nArchive v1.0.2: 3 files, 14388 bytes\n\nFiles: skill-card.md (1998b), SKILL.md (27927b), _meta.json (142b)\n\nFile v1.0.2:SKILL.md\n\n---\r\nname: \"AI Meeting Intelligence Expert\"\r\ndescription: \"AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, and distributed teams who need to capture and act on meeting insights without manual note-taking. Keywords: meeting notes, meeting transcription, action items extraction, meeting summary, decision tracking, calendar integration, agenda preparation, meeting efficiency, AI meeting assistant, 会议纪要, 会议转录, 智能摘要, 行动项提取, 会议效率, 待办跟进, 决策追踪.\"\r\nversion: \"1.0.2\"\r\n---\r\n\r\n# AI Meeting Intelligence Expert\r\n\r\n## Overview\r\n\r\nTransform chaotic meetings into structured, actionable insights. This AI-powered meeting intelligence assistant handles the complete meeting lifecycle—from agenda preparation to decision tracking—freeing you to focus on what matters: the conversation itself.\r\n\r\n## Triggers\r\n\r\n**Activate only when the request is about a meeting artefact** — an agenda, a\r\ntranscript, a set of notes, a decision log or an action-item list. The keywords\r\nbelow are necessary but not sufficient on their own.\r\n\r\n- 中文触发词：`会议纪要`、`智能会议`、`会议分析`、`会议摘要`、`提取行动项`、`会议转录`、`开会被忘`\r\n- English triggers: `meeting notes`, `meeting summary`, `transcribe meeting`, `action items`, `decision tracking`, `prepare meeting`, `meeting agenda`\r\n\r\n**Required context (at least one must be present)**\r\n\r\n1. There is a meeting artefact in the request (notes, transcript, agenda, minutes), or\r\n2. A meeting is being prepared for, or\r\n3. A decision or action item from a meeting is being tracked or followed up.\r\n\r\n**Non-triggers — do not activate for these**\r\n\r\n| Ambiguous request | Why not this skill | Route to |\r\n|---|---|---|\r\n| \"action items\" from a project plan or a document | No meeting artefact; it is task management | Project/task tooling |\r\n| \"summarise this contract / report\" | Document summarisation, not a meeting | Document summarisation skill |\r\n| \"transcribe this audio\" of a lecture or interview | Not a meeting; consent and purpose differ | Transcription tooling |\r\n| \"notes\" meaning personal study notes | No meeting, no attendees, no decisions | Note-taking app |\r\n| \"meeting room booking\" / calendar scheduling | Logistics, not content | Calendar tooling |\r\n| \"draft an email\" with no meeting source | General writing | Writing assistance |\r\n\r\n**Scope note**: this skill drafts artefacts for you to review. It does not join or\r\nrecord meetings, does not access your calendar or mailbox, and does not write files\r\nor send email without the explicit confirmation described in the next section.\r\n\r\n## Data Handling & Privacy (read first / 前置声明)\r\n\r\nMeeting content is one of the easiest ways to leak sensitive information into a\r\nmodel context. Apply these rules before pasting anything:\r\n\r\n**Data minimisation（数据最小化）**\r\n1. Paste only what is needed for the task. A 200-line verbatim transcript is\r\n rarely necessary — a structured bullet list carries the same decisions.\r\n2. Strip the following before sharing: 身份证号/护照号、银行账号、保单号、\r\n 手机号、家庭住址、薪酬数字、未公开财务数据、客户名单、医疗健康信息。\r\n3. Replace identifiers with stable pseudonyms (`客户A`、`Region-2`) and keep the\r\n mapping locally, outside the conversation.\r\n4. If a meeting is legally or regulatorily sensitive, keep processing local and\r\n do not send content to third-party services without an approved DPIA.\r\n\r\n**Save-and-send gate（保存与外发必须先预览确认）**\r\n- Never write a summary to a file, send a follow-up email, or update a tracker\r\n as a bare action. Always:\r\n 1. Show the full draft to the user,\r\n 2. Mark the items that contain personal or confidential data,\r\n 3. Wait for explicit confirmation (\"确认发送\" / \"确认保存\"),\r\n 4. Only then persist or send.\r\n- Drafts are inert until confirmed. Treat \"send\" and \"save\" as separate,\r\n individually confirmed actions.\r\n\r\n**Consent（录音与转录的同意）**\r\n- Recording and transcribing meetings requires the consent of participants;\r\n requirements differ by jurisdiction. Confirm your organisation's policy\r\n before enabling automatic transcription.\r\n\r\n**Accuracy boundary**\r\n- A summary is a lossy artifact. For anything with legal, financial or\r\n regulatory effect, the authoritative record is the approved minute, not the\r\n AI-generated draft.\r\n\r\n## Features\r\n\r\n### 1. Pre-Meeting Preparation\r\n- Generate structured meeting agendas based on topic keywords\r\n- Create attendee briefing documents from CRM/project data\r\n- Suggest time allocations for each agenda item\r\n- Provide historical context from past meeting notes\r\n\r\n\r\n**Worked example — 15-minute agenda generated from a one-line brief**\r\n\r\nBrief: `\"理赔时效专项复盘会，参会：运营、客服、IT，60 分钟\"`\r\n\r\n| Slot | Item | Owner | Min | Output expected |\r\n|---|---|---|---|---|\r\n| 0–5 | 上期行动项闭环情况 | 运营 | 5 | 3 项已闭环 / 2 项延期及原因 |\r\n| 5–20 | 时效数据：结案时长分布 | 运营 | 15 | P50 / P90 与上月对比 |\r\n| 20–40 | 卡点归因：系统与人工各占多少 | IT + 客服 | 20 | Top 3 卡点及责任方 |\r\n| 40–55 | 决策：是否调整时效考核口径 | 全体 | 15 | 明确是/否 + 生效日 |\r\n| 55–60 | 行动项与责任人确认 | 主持人 | 5 | 每项一责任人一截止日 |\r\n\r\nThe last two rows are what generic agenda generators omit: a named decision and\r\na named owner per item.\"\r\n\r\n\r\n**第二例 — 议程被压缩到 30 分钟时怎么砍**\r\n\r\n原 60 分钟议程压缩到 30 分钟时，不要按比例缩短每一项（那会让每一项都做不完），\r\n而是整段删除：保留\"决策项\"与\"行动项确认\"（共 20 分钟），把数据汇报改为会前阅读材料，\r\n卡点归因改为会后专项。判断标准很简单——**需要多人当场表态的环节必须留在会上，\r\n只需要传递信息的环节一律移出会议**。\r\n\r\n\r\n### 2. Real-Time Transcription Support\r\n- Process live meeting notes and convert to timestamped transcript\r\n- Identify and label different speakers\r\n- Flag action items, decisions, and questions in real-time\r\n- Highlight sentiment shifts during discussions\r\n\r\n\r\n**Worked example — live tagging shorthand**\r\n\r\nUse single-character marks while the meeting runs, then expand them afterwards:\r\n\r\n```\r\n[D] decision [A] action [Q] question [R] risk [T] tbd/需要补数据\r\n ↓\r\n09:12 [D] 万元以下的案件不再要求人工复核 —— 运营负责人确认\r\n09:20 [A] IT 在 9/20 前提交接口改造方案\r\n09:31 [Q] 带病体案件是否适用同一时效口径？—— 未决\r\n09:44 [R] 若 10 月上线，与年终结算并行，存在回归风险\r\n09:52 [T] 缺少 8 月分中心数据，待补\r\n```\r\n\r\nTwo rules that make the expansion reliable:\r\n- Every `[A]` must get an owner and a date before the meeting ends; an action\r\n without both is not an action.\r\n- Every `[Q]` must be either answered or carried to the next agenda. Unanswered\r\n questions that silently disappear are the main failure mode of meeting notes.\r\n\r\n**第二例 — 打断与跑题的现场处理**\r\n\r\n```\r\n10:05 [T] 话题从\"时效口径\"跳到\"系统改造预算\" —— 记为新议题，不合并\r\n10:18 [A] 预算部分另开一次会，主持人在会后 1 天内发出邀请\r\n10:22 [D] 本次会议只解决时效口径，预算不在本次决策范围\r\n```\r\n\r\n要点：跑题不等于无效。把被搁置的话题记为独立的 `[T]`，并显式记下\"本次不决策\"，\r\n比强行拉回主线更能保护会议产出——被拉回的话题往往下次会议原样重现。\r\n\r\n\r\n### 3. Post-Meeting Intelligence\r\n- Generate comprehensive meeting summaries (30-second, 1-minute, 5-minute versions)\r\n- Extract and format action items with owners and deadlines\r\n- Create follow-up email drafts for stakeholders\r\n- Update project trackers and task managers\r\n\r\n\r\n**Worked example — three summary lengths from the same meeting**\r\n\r\n| Version | Length | Reader | Contains | Must NOT contain |\r\n|---|---|---|---|---|\r\n| 30-second | 2–3 句 | 高管/未参会者 | 结论 + 金钱/时间影响 | 过程、争论细节 |\r\n| 1-minute | 1 段 | 参会者 | 结论 + 行动项 + 责任人 | 逐字引用、情绪描述 |\r\n| 5-minute | 1 页 | 项目组/审计 | 决策依据、反对意见、数据、未决问题 | 与决策无关的闲聊 |\r\n\r\nRule: the same 3 facts must appear in all three versions. If they differ, the\r\nshort version is editorialising rather than summarising.\r\n\r\n**Follow-up email micro-example**\r\n\r\n```\r\nSubject: 理赔时效专项复盘会 - 决策与你的行动项（9/10）\r\n\r\n本次确认：\r\n1. 万元以下案件取消人工复核，10/1 起生效\r\n2. 时效考核口径维持不变（未调整）\r\n\r\n你的下一步：\r\n- IT 接口改造方案 —— 9/20 前提交\r\n- 8 月分中心数据 —— 9/12 前补齐\r\n\r\n待决事项：带病体案件是否适用同一口径，下次会议定\r\n```\r\nNote the last line: unresolved items are stated as unresolved. Omitting them is\r\nwhat makes follow-ups misleading.\r\n\r\n\r\n### 4. Meeting Analytics\r\n- Track meeting frequency, duration, and attendance\r\n- Identify recurring discussion topics\r\n- Measure action item completion rates\r\n- Generate meeting ROI reports\r\n\r\n\r\n**Worked example — a quarterly meeting-health report**\r\n\r\n| Metric | This quarter | Last quarter | Read | Action if bad |\r\n|---|---|---|---|---|\r\n| 会议总时长/人/周 | 9.5 h | 11.2 h | 下降，健康 | — |\r\n| 无议程会议占比 | 41% | 38% | 恶化 | 强制模板 |\r\n| 决策会占比 | 22% | 25% | 略降 | 合并周会 |\r\n| 行动项按期完成率 | 63% | 71% | 恶化 | 减少并行项 |\r\n| 平均参会人数 | 8.4 | 7.9 | 微增 | 拆小会 |\r\n| 重复议题次数 | 6 | 3 | 翻倍 | 该议题需专项决策 |\r\n\r\nInterpretation guardrails:\r\n- A high action-completion rate with very few action items usually means the\r\n meeting produced nothing, not that the team is efficient.\r\n- \"Recurring topics\" is the strongest signal: the same topic 3+ times means it\r\n needs a decision owner, not another meeting.\r\n\r\n**第二例 — 用会议健康度数据砍掉一场会**\r\n\r\n同样的数据如果显示：`无议程会议占比 41%` 且 `决策会占比 22%`，最有效的动作通常不是\r\n\"提高会议质量\"，而是结构性调整：把每周例会改为双周，并要求无议程的会议自动取消。\r\n会议分析的输出应当落在\"会议数量与形式\"上，而不是落在\"参会者态度\"上——后者无法度量，\r\n也容易变成对个人的评价。\r\n\r\n\r\n## Workflow\r\n\r\n### Basic Meeting Summary Workflow\r\n\r\n```\r\n1. INPUT: Meeting transcript/notes/raw text\r\n ↓\r\n2. PROCESS: AI extracts key information\r\n - Speakers and roles\r\n - Topics discussed\r\n - Decisions made\r\n - Action items assigned\r\n - Questions raised\r\n ↓\r\n3. OUTPUT: Structured meeting intelligence\r\n - Executive summary\r\n - Action item list\r\n - Decision log\r\n - Follow-up recommendations\r\n```\r\n\r\n### Full Meeting Lifecycle Workflow\r\n\r\n```\r\nPhase 1: Preparation\r\n├── Receive meeting topic/context\r\n├── Generate agenda template\r\n├── Pull relevant background data\r\n└── Prepare attendee briefings\r\n\r\nPhase 2: During Meeting\r\n├── Log notes in real-time\r\n├── Mark key moments\r\n├── Track time vs. agenda\r\n└── Note unresolved items\r\n\r\nPhase 3: Post-Meeting\r\n├── Transcribe and clean up notes\r\n├── Generate summary versions\r\n├── Extract action items\r\n├── Draft follow-ups\r\n└── Update trackers\r\n\r\nPhase 4: Follow-Through\r\n├── Send summaries to attendees\r\n├── Create task reminders\r\n├── Track action item status\r\n└── Flag overdue items\r\n```\r\n\r\n## Input Examples\r\n\r\n### Example 1: Meeting Notes Input\r\n```\r\nMeeting: Q2 Product Planning\r\nDate: 2026-05-15\r\nAttendees: Sarah (PM), Mike (Eng), Lisa (Design), John (Sales)\r\n\r\nNotes:\r\n- Sarah opened with Q1 review, metrics looking good\r\n- Mike mentioned technical blockers on API integration\r\n- Lisa showed new mockups, everyone loved the dark mode\r\n- John said enterprise clients are asking for SSO\r\n- Decided to prioritize SSO for next sprint\r\n- Mike will create technical spec by Friday\r\n- Lisa to update mockups with SSO flows by next week\r\n- Sarah to schedule follow-up with enterprise team\r\n```\r\n\r\n**Expected Output:**\r\n```markdown\r\n## Meeting Summary: Q2 Product Planning\r\n\r\n### Quick Take (30 sec)\r\nQ1 metrics positive. Team aligned on Q2 priorities: SSO feature for enterprise clients. Technical spec due Friday, mockups by next week.\r\n\r\n### Decisions Made\r\n1. Prioritize SSO implementation in next sprint\r\n2. Enterprise team meeting to be scheduled\r\n\r\n### Action Items\r\n| Item | Owner | Due Date |\r\n|------|-------|----------|\r\n| Create technical spec for SSO | Mike | 2026-05-20 |\r\n| Update mockups with SSO flows | Lisa | 2026-05-22 |\r\n| Schedule enterprise team follow-up | Sarah | 2026-05-18 |\r\n\r\n### Discussion Highlights\r\n- Enterprise clients requesting SSO (high priority)\r\n- Dark mode mockups well received\r\n- API integration blockers acknowledged\r\n```\r\n\r\n### Example 2: Action Item Extraction\r\n**Input:** Raw meeting transcript or bullet points\r\n**Output:** Structured action item list with:\r\n- Task description\r\n- Assigned owner\r\n- Deadline (if mentioned)\r\n- Priority level\r\n- Related context\r\n\r\n### Example 3: Meeting Agenda Generation\r\n**Input:** \"Quarterly planning meeting with engineering and product teams\"\r\n**Output:**\r\n```markdown\r\n## Q2 Planning Meeting Agenda\r\n\r\n### Pre-Meeting (15 min)\r\n- Review Q1 OKRs and completion status\r\n- Prepare Q2 targets draft\r\n\r\n### Agenda (60 min total)\r\n1. Q1 Retrospective (15 min)\r\n - Wins to celebrate\r\n - Areas for improvement\r\n \r\n2. Q2 Goal Setting (25 min)\r\n - Product roadmap alignment\r\n - Engineering capacity planning\r\n - Resource requirements\r\n \r\n3. Team Updates (10 min)\r\n - Cross-functional dependencies\r\n - Blockers and risks\r\n \r\n4. Wrap-Up (10 min)\r\n - Confirm decisions\r\n - Assign next steps\r\n```\r\n\r\n### Example 4: 中文会议纪要（金融场景，含脱敏）\r\n\r\n**Input（用户已自行脱敏）:**\r\n```\r\n会议：医惠锡城产品定价讨论\r\n时间：2026-09-08 参会：产品部A、精算B、数据C、合规D\r\n\r\n- A：带病体承保的赔付率数据还没拿到，医保局接口预计 9 月下旬开通\r\n- B：没有带病体数据，只能先用行业经验值做区间定价，误差可能 ±15%\r\n- C：健康体部分数据已够，可以先出健康体方案\r\n- D：区间定价对外披露要谨慎，定价说明里不能出现未经验证的假设\r\n- 决定：先出健康体方案（9/20 前），带病体等数据到齐后第二版\r\n- B 负责健康体精算假设文档，9/18 前\r\n- C 负责与医保局对接，每周反馈接口进度\r\n```\r\n\r\n**Expected Output:**\r\n```markdown\r\n## 会议纪要：医惠锡城产品定价讨论（2026-09-08）\r\n\r\n### 30 秒摘要\r\n带病体赔付数据尚未获取（医保局接口预计 9 月下旬开通），会议决定分两版推进：\r\n健康体方案 9/20 前先出，带病体方案待数据齐备后出第二版。\r\n\r\n### 决策\r\n1. 采用分版推进：健康体先行（9/20 前），带病体后置\r\n2. 带病体暂不使用未经验证的行业经验值作为对外定价依据\r\n\r\n### 行动项\r\n| 事项 | 责任人 | 截止 | 交付物 |\r\n|---|---|---|---|\r\n| 健康体精算假设文档 | B（精算） | 09-18 | 假设说明 + 敏感性测试 |\r\n| 医保局接口对接周报 | C（数据） | 每周五 | 进度反馈 |\r\n| 健康体方案初稿 | A（产品） | 09-20 | 方案文档 |\r\n\r\n### 未决事项\r\n- 带病体赔付率数据来源与时效（依赖外部接口，非本团队可控）\r\n- 区间定价的对外披露口径（需合规复核）\r\n\r\n### 风险\r\n- 若接口延迟超过 10 月中旬，带病体方案将错过产品报备窗口 —— 建议 9/30 设检查点\r\n```\r\n\r\n**保存前提示**: 本纪要含产品名称与内部时间安排，属内部信息。\r\n请确认分发范围后再保存或外发；对外版本需删除\"风险\"与\"未决事项\"两节。\r\n\r\n### Example 5: 跨会议决策追踪\r\n\r\n**Input:**\r\n```\r\n我们有 6 次关于\"是否上数据中台\"的会议记录。这个决策到底定了没有？\r\n```\r\n\r\n**Output:**\r\n```\r\n决策追踪结果：未定（已讨论 6 次）\r\n\r\n| # | 日期 | 结论 | 阻塞原因 | 状态 |\r\n|---|---|---|---|---|\r\n| 1 | 06-12 | 待评估 | 需要成本测算 | 已闭环 |\r\n| 2 | 06-26 | 待评估 | 需要成本测算（未做） | 延期 |\r\n| 3 | 07-10 | 倾向做 | 需要确定牵头部门 | 未闭环 |\r\n| 4 | 07-24 | 待评估 | 牵头部门未定（重复阻塞） | 延期 |\r\n| 5 | 08-14 | 倾向做 | 预算未批 | 未闭环 |\r\n| 6 | 09-04 | 待评估 | 又回到成本测算 | 回退 |\r\n\r\n诊断：\r\n- 6 次会议中，\"成本测算\"出现 3 次、\"牵头部门\"出现 2 次，均未闭环\r\n- 这不是信息不足的问题，是没有人为这两件事负责\r\n- 会议在\"倾向做\"和\"待评估\"之间循环，属于典型的无主决策\r\n\r\n建议（不是再开一次会）：\r\n1. 指定一名决策提案人（不是会议召集人），负责写出一页纸提案\r\n2. 明确决策人与决策日期（例如 9/30 前由分管领导拍板）\r\n3. 若 9/30 无法决策，则显式记录\"本季度不做\"，并在下季度重新评估\r\n4. 第 7 次会议的议程应只含一项：拍板或明确否决\r\n\r\n给管理层的提示：重复议题超过 3 次，成本已经超过决策本身的价值。\r\n```\r\n\r\n### Example 6: A request that looks in-scope but is not\r\n\r\n**Input:**\r\n```\r\n帮我整理一下这份项目计划里的 action items。\r\n```\r\n\r\n**Output:**\r\n```\r\nThis is task management, not meeting intelligence — the source is a project plan,\r\nnot a meeting artefact, so the meeting-specific handling (consent, distribution\r\nscope, decision-vs-discussion distinction) does not apply.\r\n\r\nWhat to do instead:\r\n1. Confirm the source document and who owns its action list.\r\n2. Extract owner + due date per item; skip the decision log entirely.\r\n\r\nCome back to this skill if any of the following becomes true:\r\n- The action items originate from a meeting and you have the notes or transcript.\r\n- You need a decision log that distinguishes \"decided\" from \"discussed\".\r\n- You are preparing the agenda for the meeting where these items will be reviewed.\r\n```\r\n\r\n\r\n\r\n## Output Templates\r\n\r\n### Template 1: Meeting Summary\r\n```markdown\r\n## [Meeting Title]\r\n\r\n**Date:** [Date]\r\n**Time:** [Start] - [End]\r\n**Location:** [Room/Video Link]\r\n**Attendees:** [Names and Roles]\r\n\r\n### Executive Summary\r\n[2-3 sentence overview]\r\n\r\n### Agenda vs. Actual\r\n| Topic | Planned | Actual |\r\n|-------|---------|--------|\r\n| ... | ... | ... |\r\n\r\n### Key Decisions\r\n1. [Decision 1]\r\n2. [Decision 2]\r\n\r\n### Action Items\r\n- [ ] [Task] - @Owner - Due: [Date]\r\n- [ ] [Task] - @Owner - Due: [Date]\r\n\r\n### Open Questions\r\n- [Question 1]\r\n- [Question 2]\r\n\r\n### Next Meeting\r\n- Scheduled: [Date/Time]\r\n- Focus: [Topics]\r\n```\r\n\r\n### Template 2: Follow-Up Email\r\n```markdown\r\nSubject: [Meeting Title] - Key Decisions & Your Action Items\r\n\r\nHi [Name],\r\n\r\nFollowing up on today's [meeting name]. Here's a quick summary:\r\n\r\n**What We Decided:**\r\n- [Decision 1]\r\n- [Decision 2]\r\n\r\n**Your Next Steps:**\r\n- [Action item 1] - by [date]\r\n- [Action item 2] - by [date]\r\n\r\n**Resources:**\r\n- [Link to meeting notes]\r\n- [Link to relevant documents]\r\n\r\nLet me know if you have any questions!\r\n\r\nBest,\r\n[Your name]\r\n```\r\n\r\n## Meeting Type → Template Cheat Sheet\r\n\r\n| 会议类型 | 核心产出 | 纪要侧重 | 最常遗漏 | 分发范围 | 保存前确认点 | 建议的 AI 参与度 |\r\n|---|---|---|---|---|---|---|\r\n| 例会/站会 | 进度同步 | blockers 与变更 | 上周行动项状态 | 团队内部 | 是否含未公开排期 | 全自动：结构化后直接分发 |\r\n| 决策会 | 一个明确决策 | 决策 + 依据 + 反对意见 | 决策生效日与适用范围 | 决策相关方 | 决策表述是否与决议一致 | 半自动：决策措辞必须人工定稿 |\r\n| 评审会 | 通过/不通过 + 修改清单 | 问题清单与责任人 | 未通过项的重审时间 | 项目组 | 是否含个人绩效评价 | 半自动：问题清单可生成，结论人工填 |\r\n| 1on1 | 成长与障碍 | 约定项（不写细节） | 双方共同确认 | 仅双方 | 默认不留存细节，确认后再存 | 最低：只做格式整理，内容人工写 |\r\n| 客户/外部会议 | 承诺与下一步 | 对外承诺的准确措辞 | 内部推测被写入对外版 | 内外部版本分开 | 内外两版分别确认 | 半自动：内外部两版分别生成并人工比对 |\r\n| 复盘会 | 可复用结论 | 时间线 + 根因 + 改进项 | 谁负责跟改进项 | 相关团队 | 是否含追责性表述 | 半自动：时间线可生成，根因人工判断 |\r\n| 董事会/监管类 | 合规留痕 | 逐项决议、表决情况 | 出席与回避记录 | 法定范围 | 须与正式决议文本核对 | 最低：仅做留痕模板，须与决议文本核对 |\r\n\r\n## Integration Recommendations\r\n\r\n| Use Case | Recommended Tools | 数据敏感度 | 是否需要脱敏 | 保存/外发前的人工确认点 | 典型误用 |\r\n|---|---|---|---|---|---|\r\n| Calendar sync | Google Calendar, Outlook | 低（标题/时间） | 一般不需要 | 外部参会人是否可见 | 把议题详情写进日历标题外泄 |\r\n| Note-taking | Notion, Obsidian, Evernote | 高（全文） | 需要 | 全文预览 + 确认落库 | 未脱敏全文直接同步到云端 |\r\n| Task management | Todoist, Asana, Linear, Jira | 中（任务描述） | 视描述内容 | 任务名是否含客户名 | 把客户名写进公开看板 |\r\n| Video conferencing | Zoom, Google Meet, Teams | 高（录音/转录） | 需要 | 参会人同意 + 保留期限 | 未经同意开启自动转录 |\r\n| CRM sync | Salesforce, HubSpot | 高（客户信息） | 需要 | 字段级确认 | 把内部猜测写入客户档案 |\r\n| Email follow-ups | Gmail, Outlook | 高（对外） | 需要 | 内外部版本分别确认 | 直接发送未经确认的草稿 |\r\n| 本地归档（推荐） | 本地 Markdown / 内网 Wiki | 可控 | 视内容 | 落盘路径与权限确认 | 默认保存到公共目录 |\r\n\r\n## Ecosystem & Compliance Notes (as of 2026-09-28 / 截至 2026-09-28)\r\n\r\nVerify every item against your vendor's documentation and your own compliance\r\nfunction before acting on it.\r\n\r\n| 关注点 | 需向谁确认 | 与本技能的关系 |\r\n|---|---|---|\r\n| 会议录音/转录的告知同意要求 | 本单位合规/法务 | 决定能否开启自动转录 |\r\n| 会议记录的保存期限与归档方式 | 档案与合规部门 | 决定纪要落哪里、存多久 |\r\n| 金融/保险机构会议留痕要求 | 监管机构最新规定（以官方发布为准） | 涉及决策类会议的纪要完整性 |\r\n| 第三方会议 AI 服务的数据出境与存储地 | 供应商 DPIA/合同 | 决定能否使用云端转录 |\r\n| 生成式 AI 处理内部信息的内部政策 | 本单位 AI 治理制度 | 决定哪些内容可进入模型上下文 |\r\n| 会议 AI 生成内容的标识与可追溯要求 | 本单位 AI 治理 / 合规 | 决定纪要是否需标注 AI 参与及保留修改痕迹 |\r\n\r\n**最近动态（截至 2026-09-28，以官方最新发布为准）**\r\n1. 会议 AI 功能（实时转录、自动摘要、行动项提取）已成为主流办公与会议\r\n 平台的标配，竞争重点从\"能否生成\"转向\"生成结果能否被审计与追溯\"。\r\n2. 金融机构对会议记录留痕与可追溯性的要求持续强化，决策类会议纪要往往\r\n 需要与正式决议文本一致，AI 草稿不能替代正式记录。\r\n3. 数据最小化与本地化处理成为会议 AI 选型的常见前置条件，部分场景要求\r\n 在内网完成转录与摘要。\r\n4. 会议 AI 的\"可追溯性\"要求继续细化：越来越多机构要求纪要标注 AI 参与环节、\r\n 保留修改痕迹，并能区分\"AI 草稿\"与\"经确认的正式记录\"。\r\n5. 本地化/内网部署的会议转录与摘要方案在受监管行业的采用度上升，选型时通常把\r\n \"数据不出网\"作为硬性前置条件而非加分项。\r\n6. 以上为趋势性描述，具体义务以所在司法辖区与监管机构最新规定为准。\r\n\r\n## Best Practices\r\n\r\n### For Meeting Organizers\r\n1. Share agenda 24h before meeting\r\n2. Designate a note-taker or use AI assistance\r\n3. Start and end on time\r\n4. Review and share summary within 2 hours\r\n\r\n### For Action Item Tracking\r\n1. Assign one clear owner per item\r\n2. Set specific, achievable deadlines\r\n3. Include context for why the task matters\r\n4. Follow up within 48 hours of deadline\r\n\r\n### For Meeting Efficiency\r\n1. Default to 25 or 50-minute meetings\r\n2. Include breaks for meetings over 90 minutes\r\n3. Limit attendees to decision-makers and contributors\r\n4. Record meetings (with consent) for accurate transcription\r\n\r\n## Edge Cases & Troubleshooting\r\n\r\n### Challenge: Incomplete Notes\r\n**Solution:** Provide the AI with whatever you have—bullet points, partial transcripts, even voice memos. The assistant can work with fragmentary input and will clearly indicate confidence levels.\r\n\r\n### Challenge: Multiple Meetings in One Day\r\n**Solution:** Use the daily digest feature to get an overview of all meetings, cross-reference action items, and identify scheduling conflicts.\r\n\r\n### Challenge: Unclear Action Item Ownership\r\n**Solution:** When ambiguous, flag the item for clarification rather than assigning arbitrarily. Include a \"Verify owner\" tag.\r\n\r\n### Challenge: Confidential Discussions\r\n**Solution:** Emphasize that sensitive meetings should be handled locally. Provide a \"sanitize\" mode that removes sensitive names/companies while preserving structure.\r\n\r\n## Version History\r\n\r\n- **1.0.1** (2026-09-10)\r\n - Added \"Data Handling & Privacy\" front matter: data minimisation rules,\r\n save/send preview-and-confirm gate, consent and accuracy boundaries\r\n - Added worked examples to all four feature groups (agenda with decision+owner\r\n rows, live tagging shorthand, three summary lengths, quarterly health report)\r\n - Added \"Meeting Type → Template Cheat Sheet\" (7 meeting types, 6 columns)\r\n - Expanded integration table from 2 to 6 columns (sensitivity, masking need,\r\n human checkpoint, typical misuse)\r\n - Added Example 4 (Chinese meeting minutes with masking) and Example 5\r\n (cross-meeting decision tracking)\r\n - Added \"Ecosystem & Compliance Notes (as of 2026-09-10)\"\r\n- **1.0.2** (2026-09-28)\r\n - Narrowed the trigger section: keywords are now necessary-but-not-sufficient,\r\n with a required-context rule, a six-row non-trigger disambiguation table and\r\n an explicit scope note that the skill does not join, record, read calendars or\r\n send anything unconfirmed (SQP-1, both Chinese and English trigger sets)\r\n - Added an \"建议的 AI 参与度\" column to the meeting-type cheat sheet\r\n - Added a compliance row on AI-generated content labelling and traceability\r\n - Added a second worked example to three feature modules (agenda compression,\r\n digression handling, structural fixes from health data)\r\n - Added Example 6 showing an out-of-scope request and its routing\r\n - Ecosystem & Compliance notes updated to 2026-09-28 with two added dynamics\r\n- **1.0.0** (2026-05-15): Initial release\r\n - Core meeting summary generation\r\n - Action item extraction\r\n - Decision tracking\r\n - Basic agenda generation\r\n\r\n**Last Updated**: 2026-09-28\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn74e704j3ygjcygnpf02rdvd185js13\",\n \"slug\": \"ai-meeting-intelligence\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1790572876580\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:\n\nHelps teams prepare meeting agendas and turn meeting notes or transcripts into summaries, decisions, action items, and follow-up drafts for review.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[gechengling](https://clawhub.ai/user/gechengling)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nProject managers, executives, sales teams, and distributed teams use this skill to prepare agendas, summarize meeting material, track decisions and assigned actions, and draft follow-ups for approval.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Meeting material can disclose personal or confidential information.\n\nMitigation: Remove unnecessary sensitive details and use approved local processing for sensitive meetings.\n\nRisk: Recordings or transcripts may lack participant consent.\n\nMitigation: Confirm participant consent and organizational policy before recording or transcribing.\n\nRisk: An inaccurate or sensitive draft could be saved or shared as an official record.\n\nMitigation: Review decisions, recipients, and confidential details; require separate explicit approval before saving or sending.\n\n## Reference(s):\n\n- [AI Meeting Intelligence Expert on ClawHub](https://clawhub.ai/gechengling/skills/ai-meeting-intelligence)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Markdown agendas, meeting summaries, decision and action-item lists, analytics, and follow-up email drafts]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Drafts require user review and separate confirmation before saving or sending.]\n\n## Skill Version(s):\n\n1.0.2 (source: release evidence and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.1: 3 files, 12215 bytes\n\nFiles: skill-card.md (2338b), SKILL.md (22397b), _meta.json (142b)\n\nFile v1.0.1:SKILL.md\n\n---\r\nname: \"AI Meeting Intelligence Expert\"\r\ndescription: \"AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, and distributed teams who need to capture and act on meeting insights without manual note-taking. Keywords: meeting notes, meeting transcription, action items extraction, meeting summary, decision tracking, calendar integration, agenda preparation, meeting efficiency, AI meeting assistant, 会议纪要, 会议转录, 智能摘要, 行动项提取, 会议效率, 待办跟进, 决策追踪.\"\r\nversion: \"1.0.1\"\r\n---\r\n\r\n# AI Meeting Intelligence Expert\r\n\r\n## Overview\r\n\r\nTransform chaotic meetings into structured, actionable insights. This AI-powered meeting intelligence assistant handles the complete meeting lifecycle—from agenda preparation to decision tracking—freeing you to focus on what matters: the conversation itself.\r\n\r\n## Triggers\r\n\r\n- 中文触发词：`会议纪要`、`智能会议`、`会议分析`、`会议摘要`、`提取行动项`、`会议转录`、`开会被忘`\r\n- English triggers: `meeting notes`, `meeting summary`, `transcribe meeting`, `action items`, `decision tracking`, `prepare meeting`, `meeting agenda`\r\n\r\n## Data Handling & Privacy (read first / 前置声明)\r\n\r\nMeeting content is one of the easiest ways to leak sensitive information into a\r\nmodel context. Apply these rules before pasting anything:\r\n\r\n**Data minimisation（数据最小化）**\r\n1. Paste only what is needed for the task. A 200-line verbatim transcript is\r\n rarely necessary — a structured bullet list carries the same decisions.\r\n2. Strip the following before sharing: 身份证号/护照号、银行账号、保单号、\r\n 手机号、家庭住址、薪酬数字、未公开财务数据、客户名单、医疗健康信息。\r\n3. Replace identifiers with stable pseudonyms (`客户A`、`Region-2`) and keep the\r\n mapping locally, outside the conversation.\r\n4. If a meeting is legally or regulatorily sensitive, keep processing local and\r\n do not send content to third-party services without an approved DPIA.\r\n\r\n**Save-and-send gate（保存与外发必须先预览确认）**\r\n- Never write a summary to a file, send a follow-up email, or update a tracker\r\n as a bare action. Always:\r\n 1. Show the full draft to the user,\r\n 2. Mark the items that contain personal or confidential data,\r\n 3. Wait for explicit confirmation (\"确认发送\" / \"确认保存\"),\r\n 4. Only then persist or send.\r\n- Drafts are inert until confirmed. Treat \"send\" and \"save\" as separate,\r\n individually confirmed actions.\r\n\r\n**Consent（录音与转录的同意）**\r\n- Recording and transcribing meetings requires the consent of participants;\r\n requirements differ by jurisdiction. Confirm your organisation's policy\r\n before enabling automatic transcription.\r\n\r\n**Accuracy boundary**\r\n- A summary is a lossy artifact. For anything with legal, financial or\r\n regulatory effect, the authoritative record is the approved minute, not the\r\n AI-generated draft.\r\n\r\n## Features\r\n\r\n### 1. Pre-Meeting Preparation\r\n- Generate structured meeting agendas based on topic keywords\r\n- Create attendee briefing documents from CRM/project data\r\n- Suggest time allocations for each agenda item\r\n- Provide historical context from past meeting notes\r\n\r\n\r\n**Worked example — 15-minute agenda generated from a one-line brief**\r\n\r\nBrief: `\"理赔时效专项复盘会，参会：运营、客服、IT，60 分钟\"`\r\n\r\n| Slot | Item | Owner | Min | Output expected |\r\n|---|---|---|---|---|\r\n| 0–5 | 上期行动项闭环情况 | 运营 | 5 | 3 项已闭环 / 2 项延期及原因 |\r\n| 5–20 | 时效数据：结案时长分布 | 运营 | 15 | P50 / P90 与上月对比 |\r\n| 20–40 | 卡点归因：系统与人工各占多少 | IT + 客服 | 20 | Top 3 卡点及责任方 |\r\n| 40–55 | 决策：是否调整时效考核口径 | 全体 | 15 | 明确是/否 + 生效日 |\r\n| 55–60 | 行动项与责任人确认 | 主持人 | 5 | 每项一责任人一截止日 |\r\n\r\nThe last two rows are what generic agenda generators omit: a named decision and\r\na named owner per item.\"\r\n\r\n\r\n### 2. Real-Time Transcription Support\r\n- Process live meeting notes and convert to timestamped transcript\r\n- Identify and label different speakers\r\n- Flag action items, decisions, and questions in real-time\r\n- Highlight sentiment shifts during discussions\r\n\r\n\r\n**Worked example — live tagging shorthand**\r\n\r\nUse single-character marks while the meeting runs, then expand them afterwards:\r\n\r\n```\r\n[D] decision [A] action [Q] question [R] risk [T] tbd/需要补数据\r\n ↓\r\n09:12 [D] 万元以下的案件不再要求人工复核 —— 运营负责人确认\r\n09:20 [A] IT 在 9/20 前提交接口改造方案\r\n09:31 [Q] 带病体案件是否适用同一时效口径？—— 未决\r\n09:44 [R] 若 10 月上线，与年终结算并行，存在回归风险\r\n09:52 [T] 缺少 8 月分中心数据，待补\r\n```\r\n\r\nTwo rules that make the expansion reliable:\r\n- Every `[A]` must get an owner and a date before the meeting ends; an action\r\n without both is not an action.\r\n- Every `[Q]` must be either answered or carried to the next agenda. Unanswered\r\n questions that silently disappear are the main failure mode of meeting notes.\r\n\r\n\r\n### 3. Post-Meeting Intelligence\r\n- Generate comprehensive meeting summaries (30-second, 1-minute, 5-minute versions)\r\n- Extract and format action items with owners and deadlines\r\n- Create follow-up email drafts for stakeholders\r\n- Update project trackers and task managers\r\n\r\n\r\n**Worked example — three summary lengths from the same meeting**\r\n\r\n| Version | Length | Reader | Contains | Must NOT contain |\r\n|---|---|---|---|---|\r\n| 30-second | 2–3 句 | 高管/未参会者 | 结论 + 金钱/时间影响 | 过程、争论细节 |\r\n| 1-minute | 1 段 | 参会者 | 结论 + 行动项 + 责任人 | 逐字引用、情绪描述 |\r\n| 5-minute | 1 页 | 项目组/审计 | 决策依据、反对意见、数据、未决问题 | 与决策无关的闲聊 |\r\n\r\nRule: the same 3 facts must appear in all three versions. If they differ, the\r\nshort version is editorialising rather than summarising.\r\n\r\n**Follow-up email micro-example**\r\n\r\n```\r\nSubject: 理赔时效专项复盘会 - 决策与你的行动项（9/10）\r\n\r\n本次确认：\r\n1. 万元以下案件取消人工复核，10/1 起生效\r\n2. 时效考核口径维持不变（未调整）\r\n\r\n你的下一步：\r\n- IT 接口改造方案 —— 9/20 前提交\r\n- 8 月分中心数据 —— 9/12 前补齐\r\n\r\n待决事项：带病体案件是否适用同一口径，下次会议定\r\n```\r\nNote the last line: unresolved items are stated as unresolved. Omitting them is\r\nwhat makes follow-ups misleading.\r\n\r\n\r\n### 4. Meeting Analytics\r\n- Track meeting frequency, duration, and attendance\r\n- Identify recurring discussion topics\r\n- Measure action item completion rates\r\n- Generate meeting ROI reports\r\n\r\n\r\n**Worked example — a quarterly meeting-health report**\r\n\r\n| Metric | This quarter | Last quarter | Read | Action if bad |\r\n|---|---|---|---|---|\r\n| 会议总时长/人/周 | 9.5 h | 11.2 h | 下降，健康 | — |\r\n| 无议程会议占比 | 41% | 38% | 恶化 | 强制模板 |\r\n| 决策会占比 | 22% | 25% | 略降 | 合并周会 |\r\n| 行动项按期完成率 | 63% | 71% | 恶化 | 减少并行项 |\r\n| 平均参会人数 | 8.4 | 7.9 | 微增 | 拆小会 |\r\n| 重复议题次数 | 6 | 3 | 翻倍 | 该议题需专项决策 |\r\n\r\nInterpretation guardrails:\r\n- A high action-completion rate with very few action items usually means the\r\n meeting produced nothing, not that the team is efficient.\r\n- \"Recurring topics\" is the strongest signal: the same topic 3+ times means it\r\n needs a decision owner, not another meeting.\r\n\r\n\r\n## Workflow\r\n\r\n### Basic Meeting Summary Workflow\r\n\r\n```\r\n1. INPUT: Meeting transcript/notes/raw text\r\n ↓\r\n2. PROCESS: AI extracts key information\r\n - Speakers and roles\r\n - Topics discussed\r\n - Decisions made\r\n - Action items assigned\r\n - Questions raised\r\n ↓\r\n3. OUTPUT: Structured meeting intelligence\r\n - Executive summary\r\n - Action item list\r\n - Decision log\r\n - Follow-up recommendations\r\n```\r\n\r\n### Full Meeting Lifecycle Workflow\r\n\r\n```\r\nPhase 1: Preparation\r\n├── Receive meeting topic/context\r\n├── Generate agenda template\r\n├── Pull relevant background data\r\n└── Prepare attendee briefings\r\n\r\nPhase 2: During Meeting\r\n├── Log notes in real-time\r\n├── Mark key moments\r\n├── Track time vs. agenda\r\n└── Note unresolved items\r\n\r\nPhase 3: Post-Meeting\r\n├── Transcribe and clean up notes\r\n├── Generate summary versions\r\n├── Extract action items\r\n├── Draft follow-ups\r\n└── Update trackers\r\n\r\nPhase 4: Follow-Through\r\n├── Send summaries to attendees\r\n├── Create task reminders\r\n├── Track action item status\r\n└── Flag overdue items\r\n```\r\n\r\n## Input Examples\r\n\r\n### Example 1: Meeting Notes Input\r\n```\r\nMeeting: Q2 Product Planning\r\nDate: 2026-05-15\r\nAttendees: Sarah (PM), Mike (Eng), Lisa (Design), John (Sales)\r\n\r\nNotes:\r\n- Sarah opened with Q1 review, metrics looking good\r\n- Mike mentioned technical blockers on API integration\r\n- Lisa showed new mockups, everyone loved the dark mode\r\n- John said enterprise clients are asking for SSO\r\n- Decided to prioritize SSO for next sprint\r\n- Mike will create technical spec by Friday\r\n- Lisa to update mockups with SSO flows by next week\r\n- Sarah to schedule follow-up with enterprise team\r\n```\r\n\r\n**Expected Output:**\r\n```markdown\r\n## Meeting Summary: Q2 Product Planning\r\n\r\n### Quick Take (30 sec)\r\nQ1 metrics positive. Team aligned on Q2 priorities: SSO feature for enterprise clients. Technical spec due Friday, mockups by next week.\r\n\r\n### Decisions Made\r\n1. Prioritize SSO implementation in next sprint\r\n2. Enterprise team meeting to be scheduled\r\n\r\n### Action Items\r\n| Item | Owner | Due Date |\r\n|------|-------|----------|\r\n| Create technical spec for SSO | Mike | 2026-05-20 |\r\n| Update mockups with SSO flows | Lisa | 2026-05-22 |\r\n| Schedule enterprise team follow-up | Sarah | 2026-05-18 |\r\n\r\n### Discussion Highlights\r\n- Enterprise clients requesting SSO (high priority)\r\n- Dark mode mockups well received\r\n- API integration blockers acknowledged\r\n```\r\n\r\n### Example 2: Action Item Extraction\r\n**Input:** Raw meeting transcript or bullet points\r\n**Output:** Structured action item list with:\r\n- Task description\r\n- Assigned owner\r\n- Deadline (if mentioned)\r\n- Priority level\r\n- Related context\r\n\r\n### Example 3: Meeting Agenda Generation\r\n**Input:** \"Quarterly planning meeting with engineering and product teams\"\r\n**Output:**\r\n```markdown\r\n## Q2 Planning Meeting Agenda\r\n\r\n### Pre-Meeting (15 min)\r\n- Review Q1 OKRs and completion status\r\n- Prepare Q2 targets draft\r\n\r\n### Agenda (60 min total)\r\n1. Q1 Retrospective (15 min)\r\n - Wins to celebrate\r\n - Areas for improvement\r\n \r\n2. Q2 Goal Setting (25 min)\r\n - Product roadmap alignment\r\n - Engineering capacity planning\r\n - Resource requirements\r\n \r\n3. Team Updates (10 min)\r\n - Cross-functional dependencies\r\n - Blockers and risks\r\n \r\n4. Wrap-Up (10 min)\r\n - Confirm decisions\r\n - Assign next steps\r\n```\r\n\r\n### Example 4: 中文会议纪要（金融场景，含脱敏）\r\n\r\n**Input（用户已自行脱敏）:**\r\n```\r\n会议：医惠锡城产品定价讨论\r\n时间：2026-09-08 参会：产品部A、精算B、数据C、合规D\r\n\r\n- A：带病体承保的赔付率数据还没拿到，医保局接口预计 9 月下旬开通\r\n- B：没有带病体数据，只能先用行业经验值做区间定价，误差可能 ±15%\r\n- C：健康体部分数据已够，可以先出健康体方案\r\n- D：区间定价对外披露要谨慎，定价说明里不能出现未经验证的假设\r\n- 决定：先出健康体方案（9/20 前），带病体等数据到齐后第二版\r\n- B 负责健康体精算假设文档，9/18 前\r\n- C 负责与医保局对接，每周反馈接口进度\r\n```\r\n\r\n**Expected Output:**\r\n```markdown\r\n## 会议纪要：医惠锡城产品定价讨论（2026-09-08）\r\n\r\n### 30 秒摘要\r\n带病体赔付数据尚未获取（医保局接口预计 9 月下旬开通），会议决定分两版推进：\r\n健康体方案 9/20 前先出，带病体方案待数据齐备后出第二版。\r\n\r\n### 决策\r\n1. 采用分版推进：健康体先行（9/20 前），带病体后置\r\n2. 带病体暂不使用未经验证的行业经验值作为对外定价依据\r\n\r\n### 行动项\r\n| 事项 | 责任人 | 截止 | 交付物 |\r\n|---|---|---|---|\r\n| 健康体精算假设文档 | B（精算） | 09-18 | 假设说明 + 敏感性测试 |\r\n| 医保局接口对接周报 | C（数据） | 每周五 | 进度反馈 |\r\n| 健康体方案初稿 | A（产品） | 09-20 | 方案文档 |\r\n\r\n### 未决事项\r\n- 带病体赔付率数据来源与时效（依赖外部接口，非本团队可控）\r\n- 区间定价的对外披露口径（需合规复核）\r\n\r\n### 风险\r\n- 若接口延迟超过 10 月中旬，带病体方案将错过产品报备窗口 —— 建议 9/30 设检查点\r\n```\r\n\r\n**保存前提示**: 本纪要含产品名称与内部时间安排，属内部信息。\r\n请确认分发范围后再保存或外发；对外版本需删除\"风险\"与\"未决事项\"两节。\r\n\r\n### Example 5: 跨会议决策追踪\r\n\r\n**Input:**\r\n```\r\n我们有 6 次关于\"是否上数据中台\"的会议记录。这个决策到底定了没有？\r\n```\r\n\r\n**Output:**\r\n```\r\n决策追踪结果：未定（已讨论 6 次）\r\n\r\n| # | 日期 | 结论 | 阻塞原因 | 状态 |\r\n|---|---|---|---|---|\r\n| 1 | 06-12 | 待评估 | 需要成本测算 | 已闭环 |\r\n| 2 | 06-26 | 待评估 | 需要成本测算（未做） | 延期 |\r\n| 3 | 07-10 | 倾向做 | 需要确定牵头部门 | 未闭环 |\r\n| 4 | 07-24 | 待评估 | 牵头部门未定（重复阻塞） | 延期 |\r\n| 5 | 08-14 | 倾向做 | 预算未批 | 未闭环 |\r\n| 6 | 09-04 | 待评估 | 又回到成本测算 | 回退 |\r\n\r\n诊断：\r\n- 6 次会议中，\"成本测算\"出现 3 次、\"牵头部门\"出现 2 次，均未闭环\r\n- 这不是信息不足的问题，是没有人为这两件事负责\r\n- 会议在\"倾向做\"和\"待评估\"之间循环，属于典型的无主决策\r\n\r\n建议（不是再开一次会）：\r\n1. 指定一名决策提案人（不是会议召集人），负责写出一页纸提案\r\n2. 明确决策人与决策日期（例如 9/30 前由分管领导拍板）\r\n3. 若 9/30 无法决策，则显式记录\"本季度不做\"，并在下季度重新评估\r\n4. 第 7 次会议的议程应只含一项：拍板或明确否决\r\n\r\n给管理层的提示：重复议题超过 3 次，成本已经超过决策本身的价值。\r\n```\r\n\r\n## Output Templates\r\n\r\n### Template 1: Meeting Summary\r\n```markdown\r\n## [Meeting Title]\r\n\r\n**Date:** [Date]\r\n**Time:** [Start] - [End]\r\n**Location:** [Room/Video Link]\r\n**Attendees:** [Names and Roles]\r\n\r\n### Executive Summary\r\n[2-3 sentence overview]\r\n\r\n### Agenda vs. Actual\r\n| Topic | Planned | Actual |\r\n|-------|---------|--------|\r\n| ... | ... | ... |\r\n\r\n### Key Decisions\r\n1. [Decision 1]\r\n2. [Decision 2]\r\n\r\n### Action Items\r\n- [ ] [Task] - @Owner - Due: [Date]\r\n- [ ] [Task] - @Owner - Due: [Date]\r\n\r\n### Open Questions\r\n- [Question 1]\r\n- [Question 2]\r\n\r\n### Next Meeting\r\n- Scheduled: [Date/Time]\r\n- Focus: [Topics]\r\n```\r\n\r\n### Template 2: Follow-Up Email\r\n```markdown\r\nSubject: [Meeting Title] - Key Decisions & Your Action Items\r\n\r\nHi [Name],\r\n\r\nFollowing up on today's [meeting name]. Here's a quick summary:\r\n\r\n**What We Decided:**\r\n- [Decision 1]\r\n- [Decision 2]\r\n\r\n**Your Next Steps:**\r\n- [Action item 1] - by [date]\r\n- [Action item 2] - by [date]\r\n\r\n**Resources:**\r\n- [Link to meeting notes]\r\n- [Link to relevant documents]\r\n\r\nLet me know if you have any questions!\r\n\r\nBest,\r\n[Your name]\r\n```\r\n\r\n## Meeting Type → Template Cheat Sheet\r\n\r\n| 会议类型 | 核心产出 | 纪要侧重 | 最常遗漏 | 分发范围 | 保存前确认点 |\r\n|---|---|---|---|---|---|\r\n| 例会/站会 | 进度同步 | blockers 与变更 | 上周行动项状态 | 团队内部 | 是否含未公开排期 |\r\n| 决策会 | 一个明确决策 | 决策 + 依据 + 反对意见 | 决策生效日与适用范围 | 决策相关方 | 决策表述是否与决议一致 |\r\n| 评审会 | 通过/不通过 + 修改清单 | 问题清单与责任人 | 未通过项的重审时间 | 项目组 | 是否含个人绩效评价 |\r\n| 1on1 | 成长与障碍 | 约定项（不写细节） | 双方共同确认 | 仅双方 | 默认不留存细节，确认后再存 |\r\n| 客户/外部会议 | 承诺与下一步 | 对外承诺的准确措辞 | 内部推测被写入对外版 | 内外部版本分开 | 内外两版分别确认 |\r\n| 复盘会 | 可复用结论 | 时间线 + 根因 + 改进项 | 谁负责跟改进项 | 相关团队 | 是否含追责性表述 |\r\n| 董事会/监管类 | 合规留痕 | 逐项决议、表决情况 | 出席与回避记录 | 法定范围 | 须与正式决议文本核对 |\r\n\r\n## Integration Recommendations\r\n\r\n| Use Case | Recommended Tools | 数据敏感度 | 是否需要脱敏 | 保存/外发前的人工确认点 | 典型误用 |\r\n|---|---|---|---|---|---|\r\n| Calendar sync | Google Calendar, Outlook | 低（标题/时间） | 一般不需要 | 外部参会人是否可见 | 把议题详情写进日历标题外泄 |\r\n| Note-taking | Notion, Obsidian, Evernote | 高（全文） | 需要 | 全文预览 + 确认落库 | 未脱敏全文直接同步到云端 |\r\n| Task management | Todoist, Asana, Linear, Jira | 中（任务描述） | 视描述内容 | 任务名是否含客户名 | 把客户名写进公开看板 |\r\n| Video conferencing | Zoom, Google Meet, Teams | 高（录音/转录） | 需要 | 参会人同意 + 保留期限 | 未经同意开启自动转录 |\r\n| CRM sync | Salesforce, HubSpot | 高（客户信息） | 需要 | 字段级确认 | 把内部猜测写入客户档案 |\r\n| Email follow-ups | Gmail, Outlook | 高（对外） | 需要 | 内外部版本分别确认 | 直接发送未经确认的草稿 |\r\n| 本地归档（推荐） | 本地 Markdown / 内网 Wiki | 可控 | 视内容 | 落盘路径与权限确认 | 默认保存到公共目录 |\r\n\r\n## Ecosystem & Compliance Notes (as of 2026-09-10 / 截至 2026-09-10)\r\n\r\nVerify every item against your vendor's documentation and your own compliance\r\nfunction before acting on it.\r\n\r\n| 关注点 | 需向谁确认 | 与本技能的关系 |\r\n|---|---|---|\r\n| 会议录音/转录的告知同意要求 | 本单位合规/法务 | 决定能否开启自动转录 |\r\n| 会议记录的保存期限与归档方式 | 档案与合规部门 | 决定纪要落哪里、存多久 |\r\n| 金融/保险机构会议留痕要求 | 监管机构最新规定（以官方发布为准） | 涉及决策类会议的纪要完整性 |\r\n| 第三方会议 AI 服务的数据出境与存储地 | 供应商 DPIA/合同 | 决定能否使用云端转录 |\r\n| 生成式 AI 处理内部信息的内部政策 | 本单位 AI 治理制度 | 决定哪些内容可进入模型上下文 |\r\n\r\n**最近动态（截至 2026-09-10，以官方最新发布为准）**\r\n1. 会议 AI 功能（实时转录、自动摘要、行动项提取）已成为主流办公与会议\r\n 平台的标配，竞争重点从\"能否生成\"转向\"生成结果能否被审计与追溯\"。\r\n2. 金融机构对会议记录留痕与可追溯性的要求持续强化，决策类会议纪要往往\r\n 需要与正式决议文本一致，AI 草稿不能替代正式记录。\r\n3. 数据最小化与本地化处理成为会议 AI 选型的常见前置条件，部分场景要求\r\n 在内网完成转录与摘要。\r\n4. 以上为趋势性描述，具体义务以所在司法辖区与监管机构最新规定为准。\r\n\r\n## Best Practices\r\n\r\n### For Meeting Organizers\r\n1. Share agenda 24h before meeting\r\n2. Designate a note-taker or use AI assistance\r\n3. Start and end on time\r\n4. Review and share summary within 2 hours\r\n\r\n### For Action Item Tracking\r\n1. Assign one clear owner per item\r\n2. Set specific, achievable deadlines\r\n3. Include context for why the task matters\r\n4. Follow up within 48 hours of deadline\r\n\r\n### For Meeting Efficiency\r\n1. Default to 25 or 50-minute meetings\r\n2. Include breaks for meetings over 90 minutes\r\n3. Limit attendees to decision-makers and contributors\r\n4. Record meetings (with consent) for accurate transcription\r\n\r\n## Edge Cases & Troubleshooting\r\n\r\n### Challenge: Incomplete Notes\r\n**Solution:** Provide the AI with whatever you have—bullet points, partial transcripts, even voice memos. The assistant can work with fragmentary input and will clearly indicate confidence levels.\r\n\r\n### Challenge: Multiple Meetings in One Day\r\n**Solution:** Use the daily digest feature to get an overview of all meetings, cross-reference action items, and identify scheduling conflicts.\r\n\r\n### Challenge: Unclear Action Item Ownership\r\n**Solution:** When ambiguous, flag the item for clarification rather than assigning arbitrarily. Include a \"Verify owner\" tag.\r\n\r\n### Challenge: Confidential Discussions\r\n**Solution:** Emphasize that sensitive meetings should be handled locally. Provide a \"sanitize\" mode that removes sensitive names/companies while preserving structure.\r\n\r\n## Version History\r\n\r\n- **1.0.1** (2026-09-10)\r\n - Added \"Data Handling & Privacy\" front matter: data minimisation rules,\r\n save/send preview-and-confirm gate, consent and accuracy boundaries\r\n - Added worked examples to all four feature groups (agenda with decision+owner\r\n rows, live tagging shorthand, three summary lengths, quarterly health report)\r\n - Added \"Meeting Type → Template Cheat Sheet\" (7 meeting types, 6 columns)\r\n - Expanded integration table from 2 to 6 columns (sensitivity, masking need,\r\n human checkpoint, typical misuse)\r\n - Added Example 4 (Chinese meeting minutes with masking) and Example 5\r\n (cross-meeting decision tracking)\r\n - Added \"Ecosystem & Compliance Notes (as of 2026-09-10)\"\r\n- **1.0.0** (2026-05-15): Initial release\r\n - Core meeting summary generation\r\n - Action item extraction\r\n - Decision tracking\r\n - Basic agenda generation\r\n\r\n**Last Updated**: 2026-09-10\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn74e704j3ygjcygnpf02rdvd185js13\",\n \"slug\": \"ai-meeting-intelligence\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1789018128864\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:\n\nAI Meeting Intelligence Expert helps teams prepare agendas, structure meeting notes and transcripts, summarize discussions, extract action items, draft follow-ups, and track decisions across meetings.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[gechengling](https://clawhub.ai/user/gechengling)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nProject managers, executives, sales teams, and distributed teams use this skill to turn meeting inputs into agendas, concise summaries, action-item tables, decision logs, follow-up drafts, and meeting-health analysis.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Meeting transcripts and notes can contain personal, confidential, financial, customer, or health information.\n\nMitigation: Sanitize or pseudonymize sensitive details before use, paste only the minimum content needed, and prefer local processing for legally or regulatorily sensitive meetings.\n\nRisk: Recording or transcribing a meeting without participant consent may violate organizational policy or local requirements.\n\nMitigation: Confirm participant consent and the organization's policy before enabling automatic transcription or recording.\n\nRisk: AI-generated summaries and follow-up drafts may omit nuance or introduce inaccurate commitments.\n\nMitigation: Treat outputs as drafts, review the full content, mark sensitive items, and require explicit confirmation before saving, sending, or updating external systems.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/gechengling/skills/ai-meeting-intelligence)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown with structured tables, bullet lists, and draft follow-up messages]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs should remain drafts until the user reviews sensitive content and explicitly confirms any save, send, or external update action.]\n\n## Skill Version(s):\n\n1.0.1 (source: frontmatter and server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.0: 3 files, 5561 bytes\n\nFiles: skill-card.md (2396b), SKILL.md (9089b), _meta.json (142b)\n\nFile v1.0.0:SKILL.md\n\n---\r\nname: \"AI Meeting Intelligence Expert\"\r\ndescription: \"AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, and distributed teams who need to capture and act on meeting insights without manual note-taking. Keywords: meeting notes, meeting transcription, action items extraction, meeting summary, decision tracking, calendar integration, agenda preparation, meeting efficiency, AI meeting assistant, 会议纪要, 会议转录, 智能摘要, 行动项提取, 会议效率, 待办跟进, 决策追踪.\"\r\nversion: \"1.0.0\"\r\n---\r\n\r\n# AI Meeting Intelligence Expert\r\n\r\n## Overview\r\n\r\nTransform chaotic meetings into structured, actionable insights. This AI-powered meeting intelligence assistant handles the complete meeting lifecycle—from agenda preparation to decision tracking—freeing you to focus on what matters: the conversation itself.\r\n\r\n## Triggers\r\n\r\n- 中文触发词：`会议纪要`、`智能会议`、`会议分析`、`会议摘要`、`提取行动项`、`会议转录`、`开会被忘`\r\n- English triggers: `meeting notes`, `meeting summary`, `transcribe meeting`, `action items`, `decision tracking`, `prepare meeting`, `meeting agenda`\r\n\r\n## Features\r\n\r\n### 1. Pre-Meeting Preparation\r\n- Generate structured meeting agendas based on topic keywords\r\n- Create attendee briefing documents from CRM/project data\r\n- Suggest time allocations for each agenda item\r\n- Provide historical context from past meeting notes\r\n\r\n### 2. Real-Time Transcription Support\r\n- Process live meeting notes and convert to timestamped transcript\r\n- Identify and label different speakers\r\n- Flag action items, decisions, and questions in real-time\r\n- Highlight sentiment shifts during discussions\r\n\r\n### 3. Post-Meeting Intelligence\r\n- Generate comprehensive meeting summaries (30-second, 1-minute, 5-minute versions)\r\n- Extract and format action items with owners and deadlines\r\n- Create follow-up email drafts for stakeholders\r\n- Update project trackers and task managers\r\n\r\n### 4. Meeting Analytics\r\n- Track meeting frequency, duration, and attendance\r\n- Identify recurring discussion topics\r\n- Measure action item completion rates\r\n- Generate meeting ROI reports\r\n\r\n## Workflow\r\n\r\n### Basic Meeting Summary Workflow\r\n\r\n```\r\n1. INPUT: Meeting transcript/notes/raw text\r\n ↓\r\n2. PROCESS: AI extracts key information\r\n - Speakers and roles\r\n - Topics discussed\r\n - Decisions made\r\n - Action items assigned\r\n - Questions raised\r\n ↓\r\n3. OUTPUT: Structured meeting intelligence\r\n - Executive summary\r\n - Action item list\r\n - Decision log\r\n - Follow-up recommendations\r\n```\r\n\r\n### Full Meeting Lifecycle Workflow\r\n\r\n```\r\nPhase 1: Preparation\r\n├── Receive meeting topic/context\r\n├── Generate agenda template\r\n├── Pull relevant background data\r\n└── Prepare attendee briefings\r\n\r\nPhase 2: During Meeting\r\n├── Log notes in real-time\r\n├── Mark key moments\r\n├── Track time vs. agenda\r\n└── Note unresolved items\r\n\r\nPhase 3: Post-Meeting\r\n├── Transcribe and clean up notes\r\n├── Generate summary versions\r\n├── Extract action items\r\n├── Draft follow-ups\r\n└── Update trackers\r\n\r\nPhase 4: Follow-Through\r\n├── Send summaries to attendees\r\n├── Create task reminders\r\n├── Track action item status\r\n└── Flag overdue items\r\n```\r\n\r\n## Input Examples\r\n\r\n### Example 1: Meeting Notes Input\r\n```\r\nMeeting: Q2 Product Planning\r\nDate: 2026-05-15\r\nAttendees: Sarah (PM), Mike (Eng), Lisa (Design), John (Sales)\r\n\r\nNotes:\r\n- Sarah opened with Q1 review, metrics looking good\r\n- Mike mentioned technical blockers on API integration\r\n- Lisa showed new mockups, everyone loved the dark mode\r\n- John said enterprise clients are asking for SSO\r\n- Decided to prioritize SSO for next sprint\r\n- Mike will create technical spec by Friday\r\n- Lisa to update mockups with SSO flows by next week\r\n- Sarah to schedule follow-up with enterprise team\r\n```\r\n\r\n**Expected Output:**\r\n```markdown\r\n## Meeting Summary: Q2 Product Planning\r\n\r\n### Quick Take (30 sec)\r\nQ1 metrics positive. Team aligned on Q2 priorities: SSO feature for enterprise clients. Technical spec due Friday, mockups by next week.\r\n\r\n### Decisions Made\r\n1. Prioritize SSO implementation in next sprint\r\n2. Enterprise team meeting to be scheduled\r\n\r\n### Action Items\r\n| Item | Owner | Due Date |\r\n|------|-------|----------|\r\n| Create technical spec for SSO | Mike | 2026-05-20 |\r\n| Update mockups with SSO flows | Lisa | 2026-05-22 |\r\n| Schedule enterprise team follow-up | Sarah | 2026-05-18 |\r\n\r\n### Discussion Highlights\r\n- Enterprise clients requesting SSO (high priority)\r\n- Dark mode mockups well received\r\n- API integration blockers acknowledged\r\n```\r\n\r\n### Example 2: Action Item Extraction\r\n**Input:** Raw meeting transcript or bullet points\r\n**Output:** Structured action item list with:\r\n- Task description\r\n- Assigned owner\r\n- Deadline (if mentioned)\r\n- Priority level\r\n- Related context\r\n\r\n### Example 3: Meeting Agenda Generation\r\n**Input:** \"Quarterly planning meeting with engineering and product teams\"\r\n**Output:**\r\n```markdown\r\n## Q2 Planning Meeting Agenda\r\n\r\n### Pre-Meeting (15 min)\r\n- Review Q1 OKRs and completion status\r\n- Prepare Q2 targets draft\r\n\r\n### Agenda (60 min total)\r\n1. Q1 Retrospective (15 min)\r\n - Wins to celebrate\r\n - Areas for improvement\r\n \r\n2. Q2 Goal Setting (25 min)\r\n - Product roadmap alignment\r\n - Engineering capacity planning\r\n - Resource requirements\r\n \r\n3. Team Updates (10 min)\r\n - Cross-functional dependencies\r\n - Blockers and risks\r\n \r\n4. Wrap-Up (10 min)\r\n - Confirm decisions\r\n - Assign next steps\r\n```\r\n\r\n## Output Templates\r\n\r\n### Template 1: Meeting Summary\r\n```markdown\r\n## [Meeting Title]\r\n\r\n**Date:** [Date]\r\n**Time:** [Start] - [End]\r\n**Location:** [Room/Video Link]\r\n**Attendees:** [Names and Roles]\r\n\r\n### Executive Summary\r\n[2-3 sentence overview]\r\n\r\n### Agenda vs. Actual\r\n| Topic | Planned | Actual |\r\n|-------|---------|--------|\r\n| ... | ... | ... |\r\n\r\n### Key Decisions\r\n1. [Decision 1]\r\n2. [Decision 2]\r\n\r\n### Action Items\r\n- [ ] [Task] - @Owner - Due: [Date]\r\n- [ ] [Task] - @Owner - Due: [Date]\r\n\r\n### Open Questions\r\n- [Question 1]\r\n- [Question 2]\r\n\r\n### Next Meeting\r\n- Scheduled: [Date/Time]\r\n- Focus: [Topics]\r\n```\r\n\r\n### Template 2: Follow-Up Email\r\n```markdown\r\nSubject: [Meeting Title] - Key Decisions & Your Action Items\r\n\r\nHi [Name],\r\n\r\nFollowing up on today's [meeting name]. Here's a quick summary:\r\n\r\n**What We Decided:**\r\n- [Decision 1]\r\n- [Decision 2]\r\n\r\n**Your Next Steps:**\r\n- [Action item 1] - by [date]\r\n- [Action item 2] - by [date]\r\n\r\n**Resources:**\r\n- [Link to meeting notes]\r\n- [Link to relevant documents]\r\n\r\nLet me know if you have any questions!\r\n\r\nBest,\r\n[Your name]\r\n```\r\n\r\n## Integration Recommendations\r\n\r\n| Use Case | Recommended Tools |\r\n|----------|-------------------|\r\n| Calendar sync | Google Calendar, Outlook |\r\n| Note-taking | Notion, Obsidian, Evernote |\r\n| Task management | Todoist, Asana, Linear, Jira |\r\n| Video conferencing | Zoom, Google Meet, Teams |\r\n| CRM sync | Salesforce, HubSpot |\r\n| Email follow-ups | Gmail, Outlook |\r\n\r\n## Best Practices\r\n\r\n### For Meeting Organizers\r\n1. Share agenda 24h before meeting\r\n2. Designate a note-taker or use AI assistance\r\n3. Start and end on time\r\n4. Review and share summary within 2 hours\r\n\r\n### For Action Item Tracking\r\n1. Assign one clear owner per item\r\n2. Set specific, achievable deadlines\r\n3. Include context for why the task matters\r\n4. Follow up within 48 hours of deadline\r\n\r\n### For Meeting Efficiency\r\n1. Default to 25 or 50-minute meetings\r\n2. Include breaks for meetings over 90 minutes\r\n3. Limit attendees to decision-makers and contributors\r\n4. Record meetings (with consent) for accurate transcription\r\n\r\n## Edge Cases & Troubleshooting\r\n\r\n### Challenge: Incomplete Notes\r\n**Solution:** Provide the AI with whatever you have—bullet points, partial transcripts, even voice memos. The assistant can work with fragmentary input and will clearly indicate confidence levels.\r\n\r\n### Challenge: Multiple Meetings in One Day\r\n**Solution:** Use the daily digest feature to get an overview of all meetings, cross-reference action items, and identify scheduling conflicts.\r\n\r\n### Challenge: Unclear Action Item Ownership\r\n**Solution:** When ambiguous, flag the item for clarification rather than assigning arbitrarily. Include a \"Verify owner\" tag.\r\n\r\n### Challenge: Confidential Discussions\r\n**Solution:** Emphasize that sensitive meetings should be handled locally. Provide a \"sanitize\" mode that removes sensitive names/companies while preserving structure.\r\n\r\n## Version History\r\n\r\n- **1.0.0** (2026-05-15): Initial release\r\n - Core meeting summary generation\r\n - Action item extraction\r\n - Decision tracking\r\n - Basic agenda generation\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn74e704j3ygjcygnpf02rdvd185js13\",\n \"slug\": \"ai-meeting-intelligence\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1779192388281\n}\n\nFile v1.0.0:skill-card.md\n\n## Description:
\nAI Meeting Intelligence helps teams turn meeting notes or transcripts into summaries, action items, decisions, agendas, follow-up drafts, and meeting analytics.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[gechengling](https://clawhub.ai/user/gechengling)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nProject managers, executives, sales teams, and distributed teams use this skill to prepare meeting agendas, summarize meeting content, extract action items and decisions, draft follow-ups, and track meeting outcomes.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Meeting transcripts, attendee identities, recordings, CRM details, and follow-up emails may contain confidential or personal information.
\nMitigation: Use the skill only with participant consent and authorization, sanitize sensitive content when needed, and prefer local handling for confidential discussions.
\nRisk: Generated follow-up emails, tracker updates, action items, or integration recommendations may be incomplete or incorrect.
\nMitigation: Review generated communications and proposed updates before sending, applying, or syncing them to external tools.
\nRisk: Action item ownership can be ambiguous in partial notes or incomplete transcripts.
\nMitigation: Flag unclear owners or deadlines for clarification instead of assigning them automatically.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/gechengling/ai-meeting-intelligence)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Guidance, Configuration instructions]
\n**Output Format:** [Markdown with structured summaries, tables, checklists, and draft email text]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include meeting summaries, agenda templates, action item tables, decision logs, follow-up recommendations, and integration guidance.]
\n\n## Skill Version(s):
\n1.0.0 (source: SKILL.md frontmatter and server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: AI Meeting Intelligence Expert Owner: gechengling Summary: AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, ","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\r\nname: \"AI Meeting Intelligence Expert\"\r\ndescription: \"AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, and distributed teams who need to capture and act on meeting insights without manual note-taking. Keywords: meeting notes, meeting transcription, action items extraction, meeting summary, decision tracking, calendar integration, agenda preparation, meeting efficiency, AI meeting assistant, 会议纪要, 会议转录, 智能摘要, 行动项提取, 会议效率, 待办跟进, 决策追踪.\"\r\nversion: \"1.0.2\"\r\n---\r\n\r\n# AI Meeting Intelligence Expert\r\n\r\n## Overview\r\n\r\nTransform chaotic meetings into structured, actionable insights. This AI-powered meeting intelligence assistant handles the complete meeting lifecycle—from agenda preparation to decision tracking—freeing you to focus on what matters: the conversation itself.\r\n\r\n## Triggers\r\n\r\n**Activate only when the request is about a meeting artefact** — an agenda, a\r\ntranscript, a set of notes, a decision log or an action-item list. The keywords\r\nbelow are necessary but not sufficient on their own.\r\n\r\n- 中文触发词：`会议纪要`、`智能会议`、`会议分析`、`会议摘要`、`提取行动项`、`会议转录`、`开会被忘`\r\n- English triggers: `meeting notes`, `meeting summary`, `transcribe meeting`, `action items`, `decision tracking`, `prepare meeting`, `meeting agenda`\r\n\r\n**Required context (at least one must be present)**\r\n\r\n1. There is a meeting artefact in the request (notes, transcript, agenda, minutes), or\r\n2. A meeting is being prepared for, or\r\n3. A decision or action item from a meeting is being tracked or followed up.\r\n\r\n**Non-triggers — do not activate for these**\r\n\r\n| Ambiguous request | Why not this skill | Route to |\r\n|---|---|---|\r\n| \"action items\" from a project plan or a document | No meeting artefact; it is task management | Project/task tooling |\r\n| \"summarise this contract / report\" | Document summarisation, not a meeting | Document summarisation skill |\r\n| \"transcribe this audio\" of a lecture or interview | Not a meeting; consent and purpose differ | Transcription tooling |\r\n| \"notes\" meaning personal study notes | No meeting, no attendees, no decisions | Note-taking app |\r\n| \"meeting room booking\" / calendar scheduling | Logistics, not content | Calendar tooling |\r\n| \"draft an email\" with no meeting source | General writing | Writing assistance |\r\n\r\n**Scope note**: this skill drafts artefacts for you to review. It does not join or\r\nrecord meetings, does not access your calendar or mailbox, and does not write files\r\nor send email without the explicit confirmation described in the next section.\r\n\r\n## Data Handling & Privacy (read first / 前置声明)\r\n\r\nMeeting content is one of the easiest ways to leak sensitive information into a\r\nmodel context. Apply these rules before pasting anything:\r\n\r\n**Data m"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn74e704j3ygjcygnpf02rdvd185js13\",\n \"slug\": \"ai-meeting-intelligence\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1790572876580\n}"},{"path":"skill-card.md","content":"## Description:\n\nHelps teams prepare meeting agendas and turn meeting notes or transcripts into summaries, decisions, action items, and follow-up drafts for review.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[gechengling](https://clawhub.ai/user/gechengling)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nProject managers, executives, sales teams, and distributed teams use this skill to prepare agendas, summarize meeting material, track decisions and assigned actions, and draft follow-ups for approval.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Meeting material can disclose personal or confidential information.\n\nMitigation: Remove unnecessary sensitive details and use approved local processing for sensitive meetings.\n\nRisk: Recordings or transcripts may lack participant consent.\n\nMitigation: Confirm participant consent and organizational policy before recording or transcribing.\n\nRisk: An inaccurate or sensitive draft could be saved or shared as an official record.\n\nMitigation: Review decisions, recipients, and confidential details; require separate explicit approval before saving or sending.\n\n## Reference(s):\n\n- [AI Meeting Intelligence Expert on ClawHub](https://clawhub.ai/gechengling/skills/ai-meeting-intelligence)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Markdown agendas, meeting summaries, decision and action-item lists, analytics, and follow-up email drafts]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Drafts require user review and separate confirmation before saving or sending.]\n\n## Skill Version(s):\n\n1.0.2 (source: release evidence and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams, and distributed teams who need to capture and act on meeting insights without manual note-taking. Keywords: meeting notes, meeting transcription, action items extraction, meeting summary, decision tracking, calendar integration, agenda preparation, meeting efficiency, AI meeting assistant, 会议纪要, 会议转录, 智能摘要, 行动项提取, 会议效率, 待办跟进, 决策追踪. Skill: AI Meeting Intelligence Expert Owner: gechengling Summary: AI-powered meeting intelligence assistant — automatically transcribe, summarize, extract action items, generate follow-ups, and track decisions across your meeting lifecycle. Supports multi-language transcription, speaker identification, sentiment analysis, and integration with calendar/email tools. Built for project managers, executives, sales teams,","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1141,"uniquenessScore":46,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T21:41:35.501Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T21:41:35.501Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-13T01:46:28.354Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}