gws CLI: Events +renew helper
Renew or reactivate expiring Workspace Events subscriptions β the operational point the reference alone doesn't teach
- What
- Renew or reactivate expiring Workspace Events subscriptions β the operational point the reference alone doesn't teach
- Cost
- Free
- Needs
- the `gws` binary on the PATH (see the repo README for install options); a Google account (browser OAuth via `gws auth login`, interactive and free β the Workspace Events API generally requires a paid Google Workspace account); the `gws-shared` prerequisite skill installed first
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Curated by Skill Harbor β the `+renew` helper for Workspace Events: renew or reactivate subscriptions (`--name`, `--all`, `--within`), with the real operational advice β subscriptions expire if not renewed, and `--all` plus a cron job keeps them alive. Companion to `googleworkspace-cli-gws-events`, not a duplicate β the narrow lifecycle command vs the full API reference, same helper pattern as the lot 33 `gws-calendar` / `gws-calendar-insert` pair. By @googleworkspace, listed here with credit to its creator. Honest caveats: requires the `gws` binary and a Google account (browser OAuth is free); install the prerequisite `googleworkspace-cli-gws-shared` first. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: the `gws` binary on the PATH (see the repo README for install options); a Google account (browser OAuth via `gws auth login`, interactive and free β the Workspace Events API generally requires a paid Google Workspace account); the `gws-shared` prerequisite skill installed first Install "gws CLI: Events +renew helper" for me. Teach my agent to renew or reactivate Workspace Events subscriptions β flags --name, --all, --within β and the operational habit of keeping subscriptions alive with --all plus a cron job Repository: https://github.com/googleworkspace/cli/blob/main/skills/gws-events-renew/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-cli-gws-events-renew 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-events-renew". 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. install the gws binary, run `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.