Meeting Minutes

Problem

The pain point is not “no notes,” but scattered and inconsistent meeting records. Transcripts contain vague agreement, personal opinions, and unresolved items; generated minutes can easily present inferences as decisions. Separately rendered Markdown, Word, or diagrams may each reinterpret the same source, producing conflicting conclusions.

How It Works

The skill first normalizes meeting input into a shared minutes.json, labeling facts as confirmed, inferred, or unresolved. Confirmed resolutions, owners, dates, and formal business standards must carry source quotes and paragraph locators. It then renders Markdown or Word from validated data, and applies diagram-policy to decide whether to generate logic diagrams. Input can come from Tencent Meeting recordings and transcripts or local text materials. Tencent Meeting usage is limited to auth, recording list, and transcript reading; it does not manage meetings. Word output includes DOCX structure validation, and diagram failures do not block the main document.

Boundaries

It suits traceable, low-speculation meeting minutes, not filling gaps with common sense, inventing owners, or auto-completing policies. If Word or diagram capabilities are needed, dependency installation is shown and confirmed before execution; declining leaves Markdown output available.