π³ Watch Gmail for New Emails (gws CLI)
Watch Gmail and stream new emails as NDJSON via GCP Pub/Sub β filter by label, poll or run once
- What
- Watch Gmail and stream new emails as NDJSON via GCP Pub/Sub β filter by label, poll or run once
- Cost
- Free
- Needs
- gws CLI installed and authenticated; a paid Google Workspace account (no free tier for the gws CLI); a GCP project for Pub/Sub resources
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
Curated by Skill Harbor β π³ a gws CLI sub-command skill: watch Gmail for new emails and stream them as NDJSON through a GCP Pub/Sub topic β filter by label IDs (INBOX, UNREAD), tune the batch size and poll interval, run once or stream continuously, write each message to a separate JSON file, and clean up the Pub/Sub resources on exit. Distinct from the other gws Gmail sub-commands already listed (send, read, reply, triage): this one is for watching, not acting. By @googleworkspace, listed here with credit to its creator. Honest caveats: π³ requires a paid Google Workspace account (the gws CLI has no free tier) plus a GCP project for the Pub/Sub resources; Gmail watch registrations expire after 7 days and must be renewed. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: gws CLI installed and authenticated; a paid Google Workspace account (no free tier for the gws CLI); a GCP project for Pub/Sub resources Install "Watch Gmail for New Emails (gws CLI)" for me. Watch Gmail and stream new emails as NDJSON via GCP Pub/Sub β filter by label, poll or run once Repository: https://github.com/googleworkspace/cli/blob/main/skills/gws-gmail-watch/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-gws-gmail-watch 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 and scripts 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 and its helper files into the agent's skills directory, in a folder named "googleworkspace-gws-gmail-watch". 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. any accounts, API keys, or CLI tools mentioned in the prerequisites above). 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.