monitor-stakeholders_skill

Overview

This skill scans Gmail for recent messages involving tracked stakeholders and delivers an executive digest grouped by stakeholder category. It reads each AI workforce member's Knowledge/Stakeholder_Monitoring.md to discover who to monitor, then searches Gmail and returns a concise, actionable summary of findings. The output is prepared for a polished table formatter and highlights items requiring attention.

How this skill works

The skill runs a three-stage pipeline: load the stakeholder list from the PA's Knowledge/Stakeholder_Monitoring.md, build and execute group-level Gmail queries (default last 24 hours), then fetch threads and assemble deduplicated results. It assigns messages to stakeholder groups based on sender/recipient membership, applies monitoring-note rules to flag action items, and prepares structured records for the list-emails formatter. Timeframes, deduplication, read/unread status, attachments, and Gmail flags are all respected.

When to use it

• When you say “monitor stakeholders”, “stakeholder digest”, or similar requests.
• To check recent communications from a specific stakeholder group (e.g., “any emails from NKF?”).
• Before meetings or decisions to surface new stakeholder developments.
• To verify compliance or board-related notifications flagged in monitoring notes.
• When you want a filtered, actionable view of stakeholder activity rather than full inbox noise.

Best practices

• Maintain a current Knowledge/Stakeholder_Monitoring.md with group headings, Name/Role/Email tables, and Monitoring Notes.
• Use explicit timeframes if you need more than the default 24 hours (e.g., last 7 days).
• Keep stakeholder tables concise to avoid excessively long Gmail queries; split large groups if needed.
• Review Action Required flags and monitoring rules periodically so alerts stay relevant.
• Respect timezone settings; default is Singapore (GMT+8) unless the user specifies otherwise.

Example use cases

• Daily executive digest showing any new board or investor messages in the last 24 hours.
• Ad-hoc check: “What did Cap Vista send?” to surface their recent emails and related action items.
• Compliance monitoring: surface any ACRA, filing, or regulator correspondence matching monitoring notes.
• Pre-meeting sweep to show scheduling changes, logistics, or direct asks from key stakeholders.
• Cross-reference starred or important messages from monitored contacts before escalation.