gmail

Extracts decisions, actions, and summaries from Gmail messages.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill gmail-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gmail
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.codex/plugins/cache/openai-curated/gmail/314574a046f21938025ae443f9c6dbbd0c2c9b7a/skills/gmail
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill gmail-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Gmail inboxes accumulate long threads with decisions, follow-ups, and required actions; users need concise summaries and ready responses without risking losing important details.

Core Features & Use Cases

  • Inbox triage and urgency ranking: identify what needs attention and why.
  • Thread summaries and action extraction: produce concise status, decisions, and next steps.
  • Draft replies and forwards: generate ready-to-send messages that preserve context.
  • Explicit state control: requires user confirmation before archiving, deleting, or labeling messages.

Quick Start

Ask Gmail to summarize the latest thread and extract decisions and next actions.

Frequently Asked Questions about gmail

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract action items and decisions from long Gmail threads?

To triage a Gmail inbox and rank message urgency, the system evaluates threads to identify what needs immediate attention and why. It processes mailbox-wide workflows to surface critical follow-ups and required actions automatically.

Can I draft replies and forwards directly from a Gmail thread summary?

You can generate ready-to-send draft replies and forwards that preserve full thread context. This drafting capability produces prepared responses based on the extracted decisions and required next steps without manual copying.

Does Gmail automation require confirmation before archiving or deleting messages?

Yes, explicit user confirmation is required before mutating Gmail mailbox state such as archiving, deleting, or labeling messages. This state control ensures no messages are moved or altered without direct approval.

What is the best way to triage a Gmail inbox for follow-ups and required actions?

The best way to triage a Gmail inbox for follow-ups is to apply an automated workflow that ranks urgency and extracts required actions. This identifies what needs attention across individual threads and produces concise status summaries.

Are there limitations when using automated search workflows on Gmail threads?

Automated Gmail search workflows require native search and read capabilities plus draft tooling. A key limitation is that mutating mailbox state, including archiving or labeling, strictly requires explicit user confirmation before execution.