Chen Geng Client Meeting Notes Assistant

Problem

Insurance conversations often end up as scattered chat logs, call transcripts, and ad hoc notes. A naive summary can blur customer statements, analyst inference, and next actions, leaving little material for follow-up.

How It Works

The skill treats a meeting note as a follow-up artifact rather than a transcript:

• Separate facts from inference: track what the customer explicitly said, what is inference, and what is pending.
• Stage and actions: identify the customer's stage and define who does what next.
• Quality gate: if scenario, target, or source material is missing, return a gap list and a low-confidence draft instead of inventing a final version.

Typical outputs include a communication summary, customer profile, explicit requirements, concerns, conclusions, next actions, reminders, and send-ready follow-up messages. If the user requests image cards, it first completes the text note, then generates visual-model.json, flowing HTML, and a PNG via Playwright. Completion requires checking the PNG, HTML, and render-report.json; an unverified image is not reported as delivered.

Boundaries

It fits first interviews, solution walkthroughs, phone/video calls, follow-up records, and joint visit reviews. It should not promise closing, claims, underwriting, medical, legal, or income outcomes, and it should not present unconfirmed items as conclusions. When input is thin, the priority is asking for purpose and materials, not fabricating customer background.