recipe-save-email-to-doc
Save a Gmail message body into a Google Doc for archival or reference.
npx skills add googleworkspace/cli --skill recipe-save-email-to-doc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Save a Gmail Message to Google Docs > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-gmail`, `gws-docs` Save a Gmail message body into a Google Doc for archival or reference. ## Steps 1. Find the message: `gws gmail users messages list --params '{"userId": "me", "q": "subject:important from:boss@company.com"}' --format table` 2. Get message content: `gws gmail users messages get --params '{"userId": "me", "id": "MSG_ID"}'` 3. Create a doc with the content: `gws docs documents create --json '{"title": "Saved Email - Important Update"}'` 4. Write the email body: `gws docs +write --document-id DOC_ID --text 'From: boss@company.com Subject: Important Update [EMAIL BODY]'`
- Steps
What does the recipe-save-email-to-doc skill do?
Save a Gmail message body into a Google Doc for archival or reference.
How do I install it?
Run `npx skills add googleworkspace/cli --skill recipe-save-email-to-doc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From googleworkspace/cli, a repository with 30,193 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.