gmail-workflows

gmail-workflows is a skill for Claude Code, Codex from claude-office-skills/skills. It costs 26 tokens per session (2,645 once invoked), scanned A, original, MIT.

A set of workflows for Gmail, Google's email service, that handle attachments, labels, archiving, notifications, and Google Drive storage.

In plain words
What is it for?
Use it to save email attachments to Google Drive, apply labels, archive processed messages, send notifications, and track email metrics.
Why use it?
It reduces repetitive email handling, such as downloading files, sorting messages, and archiving completed work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to save email attachments to Google Drive, apply labels, archive processed messages, send notifications, and track email metrics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/claude-office-skills/skills/gmail-workflows
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add claude-office-skills/skills --skill gmail-workflows
Clone the repo
git clone --depth 1 https://github.com/claude-office-skills/skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for gmail-workflows

README.md
[![agentmods](https://agentmods.dev/badge/skills/claude-office-skills/skills/gmail-workflows/github.svg)](https://agentmods.dev/skills/claude-office-skills/skills/gmail-workflows)
Your own site
<a href="https://agentmods.dev/skills/claude-office-skills/skills/gmail-workflows"><img src="https://agentmods.dev/badge/skills/claude-office-skills/skills/gmail-workflows/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for gmail-workflows

Your own site · 80×15
<a href="https://agentmods.dev/skills/claude-office-skills/skills/gmail-workflows"><img src="https://agentmods.dev/badge/skills/claude-office-skills/skills/gmail-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,645 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk warn 9 Mar 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.02645
Opus 5 $0.00013 $0.01323
Sonnet 5 $0.00005 $0.00529
Haiku 4.5 $0.00003 $0.00265

Measured 11d ago against content hash 0bd1e2351368, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

gmail-workflows scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

gmail-workflows/SKILL.md · 442 lines

How it starts

The opening of the file, as written. The whole thing — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Gmail Workflows

Automate Gmail with intelligent workflows for attachment management, email organization, and Google Drive integration. Based on n8n's 7,800+ workflow templates.

Overview

This skill helps you design and implement Gmail automation workflows that:

  • Automatically save attachments to Google Drive
  • Organize emails with smart labeling
  • Archive processed emails
  • Send notifications via Slack/Email
  • Track email metrics

Core Workflow Templates

1. Gmail Attachment Manager

Purpose: Automatically extract attachments from emails and save to Google Drive

Workflow Steps:

┌─────────────┐    ┌─────────────┐    ┌─────────────┐    ┌─────────────┐
│ Gmail       │───▶│ Filter by   │───▶│ Extract     │───▶│ Upload to   │
│ Trigger     │    │ Criteria    │    │ Attachments │    │ Google Drive│
└─────────────┘    └─────────────┘    └─────────────┘    └─────────────┘
                                                                │
                         ┌─────────────┐    ┌─────────────┐    │
                         │ Send        │◀───│ Apply Label │◀───┘
                         │ Notification│    │ & Archive   │
                         └─────────────┘    └─────────────┘

Configuration:

trigger:
  type: gmail_new_email
  filters:
    has_attachment: true
    from: ["*@company.com", "*@vendor.com"]
    subject_contains: ["invoice", "report", "contract"]

actions:
  - extract_attachments:
      file_types: [pdf, xlsx, docx, csv]
      max_size_mb: 25
  
  - upload_to_drive:
      folder_path: "/Attachments/{year}/{month}"
      naming_pattern: "{filename}_{sender}_{date}"
      create_folder_if_missing: true
  
  - organize_email:
      apply_label: "Processed/Attachments"
      mark_as_read: true
      archive: true
  
  - notify:
      channel: slack
      message: "New attachment saved: {filename} from {sender}"

Best Practices:

  • Use specific sender filters to avoid processing spam
  • Set file size limits to prevent storage issues
  • Use date-based folder structure for easy retrieval
  • Enable duplicate detection to avoid redundant uploads

Read the full file on GitHub · 442 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 442 lines · 26 tokens per session scan A 0bd1e2351368

Subscribe to this mod's changes

gmail-workflows is a skill published in the GitHub repository claude-office-skills/skills (460 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 2,645 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

intent-recognition

Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embedsother (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an…

n8n-io/n8n · 146 tokens

post-build-flow

Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.

n8n-io/n8n · 53 tokens

planned-task-runtime

Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.

n8n-io/n8n · 58 tokens

config-evals

Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…

n8n-io/n8n · 80 tokens

one-off-operations

Handles one-off operations: the request is a concrete effect that happens once — export or copy data somewhere, a migration, a backfill, a cleanup — with no trigger, schedule, or reuse intent. The workflow is the vehicle, not the deliverable. Users rarely say "one-off"; infer it from the task's shape. Load before…

n8n-io/n8n · 123 tokens

debugging-executions

Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.

n8n-io/n8n · 48 tokens