Agent skill · Content & Marketing

recipe-save-email-attachments

Find Gmail messages with attachments and save them to a Google Drive folder.

googleworkspacegithub.com/googleworkspaceGitHub ↗
claude-codeApache-2.0
Install
npx skills add googleworkspace/cli --skill recipe-save-email-attachments --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 1 KB
Bundled scripts: none
Version: 0.22.5
Path: skills/recipe-save-email-attachments/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 30,193
Language: Rust
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Save Gmail Attachments to Google Drive > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-gmail`, `gws-drive` Find Gmail messages with attachments and save them to a Google Drive folder. ## Steps 1. Search for emails with attachments: `gws gmail users messages list --params '{"userId": "me", "q": "has:attachment from:client@example.com"}' --format table` 2. Get message details: `gws gmail users messages get --params '{"userId": "me", "id": "MESSAGE_ID"}'` 3. Download attachment: `gws gmail users messages attachments get --params '{"userId": "me", "messageId": "MESSAGE_ID", "id": "ATTACHMENT_ID"}'` 4. Upload to Drive folder: `gws drive +upload --file ./attachment.pdf --parent FOLDER_ID`

What's inside
Steps it walks through
  1. Steps
More from cli
All skills →
About this skill
What does the recipe-save-email-attachments skill do?

Find Gmail messages with attachments and save them to a Google Drive folder.

How do I install it?

Run `npx skills add googleworkspace/cli --skill recipe-save-email-attachments --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.

Keep going