GWS Workflow: Email to Task
Convert a Gmail message into a Google Tasks entry
- What
- Convert a Gmail message into a Google Tasks entry
- Cost
- Free
- Needs
- the gws CLI installed and authenticated; a paid Google Workspace account (no free tier for the gws CLI); read the gws-shared skill first for auth and global flags
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Curated by Skill Harbor β one cross-service workflow of the gws CLI: convert a Gmail message into a Google Tasks entry, using the email subject as the task title and the snippet as notes, in the default task list or a chosen one (--tasklist). Requires the gws CLI and a paid Google Workspace account β there is no free tier for this CLI. By @googleworkspace, listed here with credit to its creator. Honest caveats: the recipe explicitly says to confirm with the user before executing β it creates a real task; gws-shared must be read first for auth and global flags; the skill documents the command β it doesn't set up your Google Cloud auth for you. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: the gws CLI installed and authenticated; a paid Google Workspace account (no free tier for the gws CLI); read the gws-shared skill first for auth and global flags Install "GWS Workflow: Email to Task" for me. Convert a Gmail message into a Google Tasks entry Repository: https://github.com/googleworkspace/cli/blob/main/skills/gws-workflow-email-to-task/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-gws-workflow-email-to-task 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-workflow-email-to-task". 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.