Meeting Scheduler Pro
v1.0.0Manage your full meeting lifecycle by scheduling via Google Calendar, suggesting time slots, preparing briefs, generating agendas, and creating follow-up tasks.
⭐ 0· 51·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match what the files do: scripts and SKILL.md consistently implement scheduling, calendar queries/creates via the gog CLI, availability stored in config/settings.json, generation of prep/agenda/follow-up notes, and optional integrations. Required capabilities (gog, Google Calendar access, local config and notes directory) are proportionate to the stated purpose.
Instruction Scope
SKILL.md and examples explicitly instruct the agent to read/write Google Calendar via gog, optionally query Gmail via gog, perform web searches about attendees, and store meeting notes locally (meeting-notes/). Those actions are within the scheduler's stated purpose but are privacy-sensitive (email/web search/attendee names) and should be enabled only with user consent; SKILL.md and SECURITY.md do disclose these behaviors.
Install Mechanism
No install spec or remote downloads are present; the package is instruction-plus-local-scripts only. Scripts call local binaries (gog, python3, date) and create local directories/files—no external arbitrary code fetches were found.
Credentials
The skill requests no environment variables or new credentials. It relies on existing gog OAuth tokens and OpenClaw model access, which is appropriate for a calendar/AI tool. The bundle does modify its own config/settings.json to enable detected local integrations (relationship-buddy, project-manager-pro) — this is expected for optional integrations but worth being aware of.
Persistence & Privilege
The skill writes local files (meeting-notes/, config/settings.json defaults if missing) and marks scripts executable (chmod 700). always:false (no forced global presence). The skill persists meeting notes and dashboard metrics locally per its design — expected but the persistent storage of meeting content is a privacy consideration.
Assessment
This package appears to do what it says: it uses the gog CLI to read/write your Google Calendar, can optionally read Gmail and run web searches to enrich prep, and stores meeting notes locally in meeting-notes/. Before installing or enabling auto-prep, verify the following: 1) Confirm the gog CLI is the official tool you expect and check what OAuth scopes you will grant (Calendar read/write, Gmail read if enabled). 2) Inspect and edit config/settings.json to turn off prep.include_email_context or prep.include_web_search if you don't want the agent to pull email or perform web searches on attendee names. 3) Review the meeting-notes/ directory policy—these files persist locally and may contain PII; plan a retention/cleanup process. 4) Because the package source/homepage is missing, confirm the publisher identity (NormieClaw is referenced in README/SECURITY.md) before granting access to your account. 5) If you're concerned about automatic behavior, avoid enabling autonomous/automatic prep or schedule generation until you've tested the skill manually. If you want higher assurance, run the scripts in a restricted environment and inspect gog auth scopes before connecting.Like a lobster shell, security has layers — review code before you run it.
latestvk975dthr6bcv3fqbcpnfm1y5dh83z59c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.