π³ Label and Archive Emails (gws CLI)
Apply a Gmail label to matching messages and archive them out of the inbox
- What
- Apply a Gmail label to matching messages and archive them out of the inbox
- 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 searches Gmail for matching messages, applies a label to them (`messages modify` with addLabelIds), and archives them out of the inbox (removeLabelIds INBOX) to keep it clean. Distinct from the sibling recipe create-gmail-filter (lot 31): that one creates a standing Gmail filter rule that applies automatically to future mail; this one is a one-off action you run on messages that already match. 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; archiving is reversible but batch-applying labels to the wrong search results is easy β verify the query returns what you expect before modifying. 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 "Label and Archive Emails (gws CLI)" for me. Apply a Gmail label to matching messages and archive them out of the inbox Repository: https://github.com/googleworkspace/cli/blob/main/skills/recipe-label-and-archive-emails/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-recipe-label-and-archive-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-label-and-archive-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.