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:
Quick answer
Google Calendar Skill for Muse is a free Muse skill that brings Google Calendar into Muse with no MCP server required, through lightweight Python scripts with self-contained OAuth. Note that it needs a Google Workspace account, since personal Gmail accounts are not supported.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 281d88dStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/sanjay3290/ai-skills/281d88df199357e3091a3be5c743a0fca9a9ae1b/skills/google-calendar/SKILL.md Pinned version: install the code at commit 281d88df199357e3091a3be5c743a0fca9a9ae1b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (plus the scripts/ folder and requirements.txt) from the repository path into a temporary folder 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It works with an API key or a token that you provide.
What the scan found — excerpts from the install prompt
- uses API keys or tokens — 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell comm · 2. Contrôle de sécurité : examinez le SKILL.md et les scripts pour tout contenu suspect (appels réseau inatten
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 281d88d · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: files.pythonhosted.org, pypi.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : uses API keys or tokens
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.