Meeting Mastery
ReviewAudited by ClawScan on May 10, 2026.
Overview
This instruction-only meeting assistant is mostly purpose-aligned, but it asks to build persistent relationship history across contacts and meetings without clear privacy or retention limits.
Before installing, decide whether you are comfortable letting the agent access meeting notes, calendar details, attendee research, and relationship history. Keep it to drafting unless you explicitly approve sending or updating shared systems, and set clear rules for what meeting information may be remembered or forgotten.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Sensitive meeting notes, subjective impressions, attendee histories, and relationship context could be carried into future tasks or exposed in later outputs if memory is not tightly controlled.
This directs the agent to retain and reuse relationship history across future meetings. That is purpose-aligned, but it is broad and persistent, and the artifacts do not define storage, retention, deletion, exclusions, or user review controls.
**Relationship Memory** — Track history with every contact across meetings
Use explicit, user-approved storage for meeting memory; define what may be remembered, excluded, edited, and deleted; and require confirmation before reusing sensitive relationship notes.
A mistaken summary, decision log, or calendar invite could be sent or recorded if the agent acts without review.
These are normal post-meeting tasks, but if the user's agent has email, document, or calendar tools, they can mutate external systems or send business communications.
- [ ] Send summary to attendees - [ ] Update [system/doc] with decisions - [ ] Schedule follow-up meeting (if needed)
Configure the skill to draft summaries and proposed updates first, and require explicit user approval before sending emails, updating shared systems, or scheduling meetings.
If connected to broad calendar or workspace accounts, the agent may see more meeting metadata than needed for a single request.
Calendar checking is expected for a meeting assistant, but it may rely on delegated access to the user's calendar and related account data even though the registry metadata declares no primary credential.
When a Meeting is Approaching (trigger: calendar check or user request)
Grant the narrowest available calendar/workspace access and prefer per-request use over broad account-wide access where possible.