gmail-operations
Class-level Gmail and email operations: multi-account setup, OAuth, triage, extraction, archiving, attachments, unsubscribe, and touchbase workflows.
Best use case
gmail-operations is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Class-level Gmail and email operations: multi-account setup, OAuth, triage, extraction, archiving, attachments, unsubscribe, and touchbase workflows.
Teams using gmail-operations should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gmail-operations/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gmail-operations Compares
| Feature / Agent | gmail-operations | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Class-level Gmail and email operations: multi-account setup, OAuth, triage, extraction, archiving, attachments, unsubscribe, and touchbase workflows.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Gmail Operations ## When to Use Use for Gmail/himalaya setup and recurring inbox operations: triage, extraction to repositories, archive hygiene, attachment/document parsing, unsubscribe sweeps, and relationship touchbase. ## Class-Level Workflow 1. Confirm account context and OAuth/token health first. 2. Classify mail by action class: triage, extract/archive, attachment processing, unsubscribe, contact/touchbase. 3. Preserve source message identifiers in extracted artifacts. 4. Keep destructive mail actions batched and reviewable. ## Consolidated Session Learnings The `references/` directory contains archived narrow skills absorbed during the 2026-04-29 umbrella consolidation pass. Use the subsections below as the class-level index, then open the named reference when a case-specific recipe is needed. ## Absorbed Narrow Skills (2026-04-29) ### `gmail-attachment-to-document` - Former skill demoted to `references/gmail-attachment-to-document.md`. - Preserved insight: Download attachments from Gmail threads, parse their content (Excel, PDF), extract structured data, and save to target repos with proper legal scanning. ### `gmail-data-extraction` - Former skill demoted to `references/gmail-data-extraction.md`. - Preserved insight: Extract structured data from Gmail emails using REST API (no pip dependencies). Covers inbox scanning, subject line regex extraction, email text parsing, thread-aware drafting, and legal-scan-before-commit workflow. ### `gmail-email-to-repo-extraction` - Former skill demoted to `references/gmail-email-to-repo-extraction.md`. - Preserved insight: Extract structured data from Gmail inbox emails, enrich with domain-specific classification, legal-scan against deny list, commit to appropriate repo, then optionally delete originals. ### `gmail-extract-and-clean` - Former skill demoted to `references/gmail-extract-and-clean.md`. - Preserved insight: Extract emails from Gmail to /mnt/ace/<repo>/, archive to appropriate workspace-hub external repos, commit, then delete from inbox. Uses email-routing.yaml for sender→repo routing. ### `gmail-extract-archive` - Former skill demoted to `references/gmail-extract-archive.md`. - Preserved insight: Extract Gmail data into a structured archive repo, parse attachments, legal scan, then delete from inbox. Single source of truth for all email data across 3 accounts. ### `gmail-headless-oauth` - Former skill demoted to `references/gmail-headless-oauth.md`. - Preserved insight: Manual OAuth2 token exchange for Gmail on headless servers. Bypass gmail-mcp-multiauth browser requirement. Generate auth URLs, exchange codes, manage multi-account credentials with auto-refresh. ### `gmail-multi-account` - Former skill demoted to `references/gmail-multi-account.md`. - Preserved insight: Multi-account Gmail management via himalaya CLI. Three accounts (aceengineer, achantav, skestates) with distinct triage rules, contact DBs, and tone profiles. Foundation skill for email automation. ### `gmail-touchbase` - Former skill demoted to `references/gmail-touchbase.md`. - Preserved insight: Periodic relationship maintenance via email — identify contacts due for outreach, draft personalized check-ins, queue for user approval. Supports per-account tone and cadence. ### `gmail-triage` - Former skill demoted to `references/gmail-triage.md`. - Preserved insight: Daily multi-account Gmail inbox triage — scan unread, classify by urgency, cross-reference contacts, generate actionable digest. Supports ace/personal/skestates accounts. ### `gmail-unsubscribe` - Former skill demoted to `references/gmail-unsubscribe.md`. - Preserved insight: Identify and batch-unsubscribe from newsletters and marketing emails across Gmail accounts. Scans List-Unsubscribe headers, generates candidates, executes with user approval. ### `contact-manager` - Former skill demoted to `references/contact-manager.md`. - Preserved insight: Normalize, classify, and manage contact databases across 3 Gmail accounts. Clean CSV exports, deduplicate, tag categories, flag touchbase/unsubscribe candidates.
Related Skills
memory-bridge-operations
Operate and recover the Hermes-to-repo memory bridge: drift checks, quality gate, bridge commits, push verification, and stash recovery when pre-bridge scripts fail after generating outputs.
github-issue-lifecycle-operations
Class-level GitHub issue lifecycle operations: issue creation, planning/execution routing, labels, evidence fields, roadmap anchors, closeout races, and visual planning.
gmail-triage
Daily multi-account Gmail inbox triage — scan unread, classify by urgency, cross-reference contacts, generate actionable digest. Supports ace/personal/skestates accounts.
gmail-outreach
Outbound email actions — periodic relationship touchbase messages and batch unsubscribe from newsletters/marketing. Combines gmail-touchbase + gmail-unsubscribe into one skill.
gmail-multi-account
Multi-account Gmail management via himalaya CLI. Three accounts (aceengineer, achantav, skestates) with distinct triage rules, contact DBs, and tone profiles. Foundation skill for email automation.
gmail-headless-oauth
Manual OAuth2 token exchange for Gmail on headless servers. Bypass gmail-mcp-multiauth browser requirement. Generate auth URLs, exchange codes, manage multi-account credentials with auto-refresh.
gmail-extract-and-act
The email-as-queue workflow — extract structured data from emails, act on it, track thread state, and delete emails when topics complete. Email is transient; extracted data is persistent.
gmail-attachment-to-document
Download attachments from Gmail threads, parse their content (Excel, PDF), extract structured data, and save to target repos with proper legal scanning.
gmail-unsubscribe
Identify and batch-unsubscribe from newsletters and marketing emails across Gmail accounts. Scans List-Unsubscribe headers, generates candidates, executes with user approval.
gmail-touchbase
Periodic relationship maintenance via email — identify contacts due for outreach, draft personalized check-ins, queue for user approval. Supports per-account tone and cadence.
gmail-extract-archive
DEPRECATED — superseded by gmail-extract-and-act. Extract Gmail data into archive repo, parse attachments, legal scan, then delete. Uses archive-everything model.
gmail-extract-and-clean
DEPRECATED — superseded by gmail-extract-and-act. Extract emails from Gmail to /mnt/ace/<repo>/, archive to repos, commit, then delete. Uses archive-everything model.