gws CLI: Calendar Event Creator
One-command Google Calendar event creation with required flags and a write caution
- What
- One-command Google Calendar event creation with required flags and a write caution
- Cost
- Free
- Needs
- the `gws` binary on the PATH; a Google account with browser OAuth (`gws auth login`) or a service account; install the googleworkspace-cli-gws-shared skill first
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the `gws calendar +insert` write helper: create a Google Calendar event in one command with required flags (`--summary`, `--start`, `--end` in RFC3339), optional attendees, location, description and a `--meet` flag that auto-attaches a Google Meet link. It carries an explicit write-command caution — confirm with the user before executing — and points back to the sibling `googleworkspace-cli-gws-calendar` fiche for everything beyond single-event creation. Read `googleworkspace-cli-gws-shared` first (auth, `--dry-run`, security rules). Distinct from the lot 31 googleworkspace workflow fiches (thin CLI helper, not a persona workflow). By @googleworkspace, listed here with credit to its creator. Honest caveats: a write command by design — the shared rules (confirm before executing, prefer `--dry-run`) matter here; browser OAuth is free, service accounts need a Google Cloud project. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: the `gws` binary on the PATH; a Google account with browser OAuth (`gws auth login`) or a service account; install the googleworkspace-cli-gws-shared skill first Install "gws CLI: Calendar Event Creator" for me. Give my agent the one-command event-creation helper for the gws CLI — create Google Calendar events with required flags and a write caution Repository: https://github.com/googleworkspace/cli/blob/main/skills/gws-calendar-insert/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-cli-gws-calendar-insert skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "googleworkspace-cli-gws-calendar-insert". 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. `gws auth login`). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. 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.