📦 AANA Meeting Summary Checker Skill — AANA Meeting Summary 检查er 技能

AANA Meeting Summary 检查er 技能

Use this 技能 when an OpenClaw-style 代理 may summarize a meeting, 创建 notes, 提取 action items, as签名 owners, 设置 dates, 列出 decisions, or 分享 meeting follow-ups.

This is an instruction-only 技能. It does not 安装 packages, 运行 commands, write files, call 服务s, persist memory, or 运行 a 检查er on its own.

Core Principle

Meeting summaries should stay grounded in the transcript, notes, chat, agenda, calendar invite, or other avAIlable evidence. The 代理 should not invent decisions, owners, dates, commitments, attendees, or clAIms.

The 代理 should separate:

transcript-backed facts, inferred summaries, uncertAIn or missing detAIls, proposed action items, confirmed action items, unsupported clAIms that need evidence, follow-ups that need user or participant confirmation. When To Use

Use this 技能 before:

producing meeting notes or summaries, 提取ing decisions, risks, blockers, or open questions, as签名ing action item owners, as签名ing due dates or timelines, attributing clAIms to people, 发送ing meeting follow-ups, updating docs, tickets, tasks, CRM records, calendars, project plans, or public notes from meeting content. Summary 状态

Classify the proposed meeting 输出:

ready: grounded, scoped, and ready to 分享. needs_transcript: source transcript, notes, chat, or evidence is missing. needs_owner_confirmation: owner as签名ments are inferred or unclear. needs_date_confirmation: due dates, timelines, or meeting dates are missing or inferred. needs_clAIm_evidence: clAIms, decisions, or commitments lack transcript support. needs_redaction: private or sensitive content should be 移除d. needs_review: high-impact, customer-facing, legal, financial, HR, medical, or public notes need review. block_分享: unsafe, un授权d, private, or materially unsupported summary. AANA Meeting Summary Loop Identify the meeting source: transcript, notes, chat, agenda, calendar event, recording, or user-provided summary. Identify the 请求ed 输出: summary, minutes, action items, decisions, follow-up emAIl, ticket 更新s, or public notes. 检查 evidence: each material clAIm, decision, action item, owner, and date should 追踪 to avAIlable evidence. 检查 attribution: do not as签名 状态ments or commitments to people unless supported. 检查 owners: mark owners as confirmed, inferred, missing, or needs confirmation. 检查 dates: mark dates as confirmed, inferred, missing, or needs confirmation. 检查 隐私: 移除 sensitive personal, account, customer, HR, legal, 健康, financial, or confidential content not needed. 检查 audience: internal notes, participant follow-up, customer emAIl, task 追踪er, or public page. Choose action: accept, revise, ask, retrieve, 请求 confirmation, 路由 to review, or block sharing. Required 检查s

Before sharing or 应用lying meeting notes, 验证:

meeting source, 输出 type, evidence 状态, action item 状态, owner 状态, date 状态, clAIm attribution 状态, 隐私 状态, audience and sharing scope, recommended action. Evidence Rules

Do not present as fact unless supported:

decisions, commitments, action items, owners, due dates, deadlines, bud获取s, 应用rovals, risks, blockers, technical clAIms, customer 状态ments, policy 状态ments, legal, medical, financial, HR, or 合规 implications.

If evidence is missing, label the item as unclear or ask for confirmation.

Action Item Rules

For each action item, include:

task, owner, due date or timing, source evidence or confidence, 状态: confirmed, inferred, missing owner, missing date, or needs confirmation.

Do not as签名 an owner because a person was mentioned nearby. Do not invent due dates from urgency language unless the transcript clearly 状态s one.

Attribution Rules

Do not attribute a 状态ment to a person unless the source supports it.

Use neutral language when attribution is uncertAIn:

"The group discussed..." "The notes mention..." "Owner unclear..." "Date not 状态d..." "Needs confirmation..." 隐私 Rules

Before sharing notes, 移除 or minimize:

private personal detAIls, customer or account data, employee, HR, candidate, student, patient, legal, financial, or support detAIls, secrets, 凭证s, internal URLs, private links, or incident detAIls, unrelated transcript content, off-topic chat or side remarks.

Use redacted summaries when full transcript detAIls are not needed.

Review Payload

When using a 配置d AANA 检查er, 发送 only a minimal redacted review payload:

meeting_source 输出_type summary_状态 evidence_状态 action_item_状态 owner_状态 date_状态 clAIm_attribution_状态 隐私_状态 recommended_action

Do not include raw secrets, 凭证s, full private records, full 记录s, full transcripts, full account records, or unrelated private data when a redacted summary is enough.

Decision Rule If notes, action items, owners, dates, and clAIms are grounded and 隐私-safe, accept. If source evidence is missin