π³ Save Email to Doc (gws CLI)
Archive a Gmail message body into a Google Doc
- What
- Archive a Gmail message body into a Google Doc
- Cost
- Free
- Needs
- a paid Google Workspace account; the gws CLI installed and authenticated; this recipe also requires the gws-gmail and gws-docs utility skills 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 a Gmail message, fetches its content, creates a Google Doc and writes the email body into it for archival or reference. Complementary to the sibling recipe save-email-attachments (lot 31): that one saves the message's attachments to Drive; this one saves the message body to a Doc β run both for a complete archive. Also the reverse of the sibling draft-email-from-doc (Doc β email). By @googleworkspace, listed here with credit to its creator. Honest caveats: the recipe assumes the gws-gmail and gws-docs utility skills are loaded and the gws binary is installed and authenticated; only the body is saved β metadata like headers and threading context are written as plain text, not preserved as email structure. 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 and gws-docs utility skills loaded Install "Save Email to Doc (gws CLI)" for me. Archive a Gmail message body into a Google Doc Repository: https://github.com/googleworkspace/cli/blob/main/skills/recipe-save-email-to-doc/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-recipe-save-email-to-doc 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-save-email-to-doc". 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.