Meeting Coordinator - In Person + Virtual (Google Meet)
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill's requirements, instructions, and included scripts are coherent with an executive scheduling assistant that uses a local gog CLI and Google Places; nothing requests unrelated credentials or hidden endpoints.
This skill appears coherent for scheduling using a local agent Gmail account and Google Places. Before installing: (1) ensure you use a dedicated, low-privilege agent Gmail account (do not give it your personal/work primary account); (2) review the contents of $HOME/.config/gog and $HOME/.config/goplaces to understand stored OAuth tokens and limit their permissions; (3) audit and trust the gog and goplaces CLIs you will install—these CLIs have network access and will act with the supplied credentials; (4) confirm you are comfortable with meeting records being stored locally under memory/scheduling/; and (5) test in a safe environment (shared calendar with write permission to the agent account) to verify the approval gates are enforced in your workflow. The included Python scripts use subprocess.run with argument lists (not a shell string), which reduces shell-injection risk, but you should still avoid exposing untrusted inputs as CLI arguments and review the scripts if you expect untrusted inputs.
Static analysis
Static analysis findings are pending for this release.
VirusTotal
66/66 vendors flagged this skill as clean.
Risk analysis
No visible risk-analysis findings were reported for this release.
