Google Calendar Skill for Muse
Google Calendar in Muse, no MCP server required β Workspace accounts.
- What
- Google Calendar in Muse, no MCP server required β Workspace accounts.
- Cost
- Free
- Needs
- A Google Workspace account (personal Gmail accounts are NOT supported), Python 3 with pip packages, and a one-time browser OAuth flow.
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Paid service required β needs a Google Workspace account (personal Gmail accounts are not supported). Curated by Skill Harbor β a free, open-source skill (Apache-2.0) by @sanjay3290, listed here with credit to its creator. A lightweight Google Calendar integration through provided Python scripts, with self-contained OAuth (no MCP server required): list calendars, list, view, create, update, and delete events with attendees, locations, and descriptions, find free slots across participants, and RSVP to invitations (accepted/declined/tentative). Tokens live in the system keychain (macOS Keychain, Windows Credential Locker, Linux Secret Service) with automatic refresh. Discovered via skills.sh. Honest note: a Google Workspace account is required β personal Gmail accounts are excluded β plus Python 3 with pip packages and a one-time browser OAuth flow. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Version:
Install
Prerequisites: A Google Workspace account (personal Gmail accounts are NOT supported), Python 3 with pip packages, and a one-time browser OAuth flow. Install "Google Calendar Skill for Muse" for me. Manage Google Calendar from Muse with no MCP server: list calendars and events, create/update/delete events with attendees and locations, find free time across participants, and RSVP to invitations. Repository: https://github.com/sanjay3290/ai-skills/blob/HEAD/skills/google-calendar/SKILL.md 1. Fetch the SKILL.md file (plus the scripts/ folder and requirements.txt) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the system keychain. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md, the scripts/ folder, and requirements.txt into the agent's skills directory, in a folder named "google-calendar". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. run the OAuth flow in my browser with my Workspace account). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.