Google Workspace Events: Renew/reactivate Workspace Events subscriptions.
a3768d0PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Renew/reactivate Workspace Events subscriptions
gws events +renew
| Flag | Required | Default | Description |
|------|----------|---------|-------------|
| --name | — | — | Subscription name to reactivate (e.g., subscriptions/SUB_ID) |
| --all | — | — | Renew all subscriptions expiring within --within window |
| --within | — | 1h | Time window for --all (e.g., 1h, 30m, 2d) |
gws events +renew --name subscriptions/SUB_ID
gws events +renew --all --within 2d
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/gws-events-renew · pinned to the source commit
git clone https://github.com/googleworkspace/cli.git
cd cli
git checkout a3768d0e82ad83cca2da97724e46bea4ff0e6dbd
mkdir -p ".claude/skills/gws-events-renew"
cp -r "skills/gws-events-renew" ".claude/skills/gws-events-renew"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit a3768d0e82ad. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b