π³ Forward Labeled Emails (gws CLI)
Batch-forward every Gmail message carrying a given label to another address
- What
- Batch-forward every Gmail message carrying a given label to another address
- Cost
- Free
- Needs
- a paid Google Workspace account; the gws CLI installed and authenticated; this recipe also requires the gws-gmail utility skill loaded
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Requires a paid Google Workspace account for the gws CLI β no free tier. Curated by Skill Harbor β a step-by-step recipe that finds all Gmail messages carrying a specific label (`label:needs-review`), fetches each one's content, and forwards it as a new email to another address. Distinct from the already-listed googleworkspace-gws-gmail-forward: that is a single-message forward utility (`+forward` on one message ID with attachments and draft mode); this is a batch workflow that forwards every message under a label. By @googleworkspace, listed here with credit to its creator. Honest caveats: the recipe assumes the gws-gmail utility skill is loaded and the gws binary is installed and authenticated; forwarding happens as new sends from your account β bulk-forwarding a large label will send many emails and may trip Gmail sending limits, and forwarded content leaves your mailbox, so verify the label and recipient first. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a paid Google Workspace account; the gws CLI installed and authenticated; this recipe also requires the gws-gmail utility skill loaded Install "Forward Labeled Emails (gws CLI)" for me. Batch-forward every Gmail message carrying a given label to another address Repository: https://github.com/googleworkspace/cli/blob/main/skills/recipe-forward-labeled-emails/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-recipe-forward-labeled-emails 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-recipe-forward-labeled-emails". 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.