← back to browse

calendar-manager

Google Calendar briefing, meeting prep, and a memory of how you work.

version
0.1.0
author
capthvnsen
license
MIT
hermes
>=0.12.0
pinned
v0.1.0
hermes profile install github.com/capthvnsen/hermes-profile-calendar-manager#v0.1.0

Install the calendar-manager bot profile from profiles for bots. Resolve it at https://profiles-for-bots-resolver.alex-ac8.workers.dev/r/calendar-manager.json, then run the installCommand it returns. It installs 1 MCP server and 2 cron jobs.

WHAT THIS INSTALLS

modelnot declared
skills5: briefing, calendar-setup, debrief, meeting-prep, needs
cron2 scheduled jobs run unattended: evening-debrief (0 17 * * 1-5), morning-brief (0 7 * * 1-5)
mcp1 server: google-calendar (spawns a local process)
hooksnone
envGOOGLE_OAUTH_CREDENTIALS

Profiles are code. Installing one can run scheduled jobs, spawn local processes, and execute shell scripts on your machine. Nothing here is vetted or sandboxed. Read the source at v0.1.0 before you run it.

README

calendar-manager

A chief-of-staff for your time. It reads Google Calendar, preps meetings, and keeps a living model of how you work. This is a profile, not a skill file.

npx profiles-for-bots install calendar-manager

or

hermes profile install github.com/capthvnsen/hermes-profile-calendar-manager#v0.1.0

Google Calendar (required)

Credentials never live in this git repo.

  1. Google Cloud Console: enable Calendar API, create an OAuth client ID of type Desktop, download the JSON.
  2. Save it outside the profile, for example ~/.config/google-calendar-mcp/gcp-oauth.keys.json.
  3. In ~/.hermes/profiles/calendar-manager/.env:
GOOGLE_OAUTH_CREDENTIALS=/absolute/path/to/gcp-oauth.keys.json
  1. On your machine:
npx -y @cocal/google-calendar-mcp auth
  1. hermes -p calendar-manager setup, then chat.

Delete-event is not enabled. The agent may propose times. It may not wipe your calendar.

Cron is cloned, not auto-enabled (hermes -p calendar-manager cron list).

What it will do

  • Weekday morning briefing from the live calendar
  • Tight meeting prep, not dossiers
  • workspace/needs.md as a model of you
  • Evening debrief notes

MCP: one local npx process (@cocal/google-calendar-mcp). That is privileged. Read the trust panel.