How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

gmail-pending-replies.en - Prompt

Name: gmail-pending-replies.en
Author: minicoohei

Prompt file imported from minicoohei/ai-agent-camp (.cursor/commands/utility/gmail-pending-replies.en.md). Copyright stays with the author.

Gmail Pending Replies - Extract Unreplied Emails

Extract emails that need a reply from Gmail and automatically generate reply drafts.

Target Categories

Unreplied emails: Emails addressed to you (TO/CC) that you haven't replied to
Thread replies: Threads you started where the last reply is from someone else

Data Sources

Method 1: Use Synced Data (Recommended)

Analyze Markdown files synced to output/gmail/{account_name}/.

Account	Path	Your Address
default	`output/gmail/default/`	`user@example.com`
work	`output/gmail/work/`	Corresponding address

Method 2: Via API (When GMAIL_ACCOUNTS_CONFIG Is Set)

python src/get_gmail_pending_replies.py --days {days}

Steps

Step 1: Extract Parameters

Extract the following from the user's input:

Days: Number of target days (default: 7)
Account: Specific account only (default: all)
Output format: markdown / json (default: screen display)

Step 2: Scan Emails

Analyze synced data at output/gmail/{account}/YYYY-MM-DD/*.md and extract:

Received emails from people other than yourself
Exclude notification emails (noreply, bank, peatix, etc.)
Exclude meeting invitations (.ics attachments)
Exclude emails with the same subject where you've already replied

Step 3: Display Results + Auto-Generate Reply Drafts

Display the list of unreplied emails
Analyze the content of each email and determine its type:
- Request/Task: Something requiring a specific action
- Question: Something requiring an answer
- Information sharing: No reply needed (shared via CC, etc.)
Automatically generate reply drafts for request and question emails:
- Read the email body
- Reference related project information if available
- Create an appropriate reply draft

Options

Option	Description	Default
`--days INT` / `-d`	Number of target days	7
`--account TEXT` / `-a`	Specific account only (label name)	all
`--output PATH` / `-o`	Output file path (.json / .md)	stdout

Usage Examples

Basic execution

/gmail-pending-replies

Runs with default settings (7 days, all accounts).

Specify number of days

/gmail-pending-replies 3 days

Runs with --days 3.

Specific account only

/gmail-pending-replies personal account only

Runs with --account personal.

Save as Markdown

/gmail-pending-replies save to output/pending.md

Runs with --output output/pending.md.

Prerequisites

When Using Synced Data (Recommended)

Emails must be synced to output/gmail/{account_name}/.

output/gmail/
├── my-account/
│   ├── 2026-01-27/
│   │   ├── index.md          # Daily index
│   │   ├── 19bfd03adcbf0235.md  # Individual email
│   │   └── ...
│   └── ...
└── work/
    └── ...

Format of each email file:

---
id: 19bfd03adcbf0235
subject: Subject
from: Sender <email@example.com>
date: 2026-01-27 10:13:51
attachments: file1.pdf, file2.xlsx  # Optional
---

# Subject

Email body...

When Using API (Optional)

The GMAIL_ACCOUNTS_CONFIG environment variable must be set with multi-account configuration:

{
  "accounts": [
    {
      "label": "work",
      "type": "service_account",
      "subject": "user@company.com"
    },
    {
      "label": "personal",
      "type": "oauth",
      "client_id_env": "GMAIL_PERSONAL_CLIENT_ID",
      "client_secret_env": "GMAIL_PERSONAL_CLIENT_SECRET",
      "refresh_token_env": "GMAIL_PERSONAL_REFRESH_TOKEN"
    }
  ]
}

Output Format

1. Unreplied Email List

Emails requiring a reply (default): 2 items
Target period: Past 7 days

======================================================================

1. About the project progress report - Action required
   Date: 2026-01-27 10:13
   From: Taro Yamada <taro.yamada@example.com>
   Type: Request/Task
   Summary: Report review request
   Link: https://mail.google.com/mail/u/0/#inbox/xxx

2. About the monthly meeting agenda
   Date: 2026-01-23 13:53
   From: Hanako Sato <hanako.sato@example.com>
   Type: Information sharing (CC)
   Summary: Agenda draft sharing
   Link: https://mail.google.com/mail/u/0/#inbox/yyy

======================================================================

2. Auto-Generated Reply Drafts (for request/question emails only)

Reply drafts are automatically generated for emails containing requests or questions:

---
## Reply Draft: About the project progress report

Subject: Re: About the project progress report

Dear Mr. Yamada,

Thank you for reaching out.
I acknowledge your request for the report.

I'm planning to prepare the report in the following categories:

[1. Information gathering/search]
- Cross-search and summary generation for Slack/Gmail/Calendar

[2. Document/material creation]
- Automatic generation of workflow diagrams

[3. Formatting/transcription]
- Data cleansing and format conversion

I will send the materials by the end of this week.
---

Exclusion Patterns

The following emails are automatically excluded:

Category	Example Patterns
Notifications	noreply, no-reply, notification
Banks	@bank.gmo-aozora.com
Events	@peatix.com, @morningpitch.com
Auto-sent	spamdigest, Moderator
Meeting invitations	.ics attachments, teams.microsoft.com

Related Commands

/extract-tasks - Task extraction from multiple sources (includes Gmail)
/slack-pending-replies - Slack version of unreplied message extraction

Install gmail-pending-replies.en and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Gmail Pending Replies - Extract Unreplied Emails Extract emails that need a reply from Gmail and **automatically generate reply drafts**. ## Target Categories 1. **Unreplied emails**: Emails addressed to you (TO/CC) that you haven't replied to 2. **Thread replies**: Threads you started where the last reply is from someone else ## Data Sources ### Method 1: Use Synced Data (Recommended) Analyze Markdown files synced to `output/gmail/{account_name}/`. | Account | Path | Your Address | |---------|------|-------------| | default | `output/gmail/default/` | `user@example.com` | | work | `output/gmail/work/` | Corresponding address | ### Method 2: Via API (When GMAIL_ACCOUNTS_CONFIG Is Set) ```bash python src/get_gmail_pending_replies.py --days {days} ``` ## Steps ### Step 1: Extract Parameters Extract the following from the user's input: - **Days**: Number of target days (default: 7) - **Account**: Specific account only (default: all) - **Output format**: markdown / json (default: screen display) ### Step 2: Scan Emails Analyze synced data at `output/gmail/{account}/YYYY-MM-DD/*.md` and extract: - Received emails from people other than yourself - Exclude notification emails (noreply, bank, peatix, etc.) - Exclude meeting invitations (.ics attachments) - Exclude emails with the same subject where you've already replied ### Step 3: Display Results + Auto-Generate Reply Drafts 1. Display the list of unreplied emails 2. **Analyze the content of each email and determine its type**: - **Request/Task**: Something requiring a specific action - **Question**: Something requiring an answer - **Information sharing**: No reply needed (shared via CC, etc.) 3. **Automatically generate reply drafts for request and question emails**: - Read the email body - Reference related project information if available - Create an appropriate reply draft ## Options | Option | Description | Default | |--------|-------------|---------| | `--days INT` / `-d` | Number of target days | 7 | | `--account TEXT` / `-a` | Specific account only (label name) | all | | `--output PATH` / `-o` | Output file path (.json / .md) | stdout | ## Usage Examples ### Basic execution ``` /gmail-pending-replies ``` Runs with default settings (7 days, all accounts). ### Specify number of days ``` /gmail-pending-replies 3 days ``` Runs with `--days 3`. ### Specific account only ``` /gmail-pending-replies personal account only ``` Runs with `--account personal`. ### Save as Markdown ``` /gmail-pending-replies save to output/pending.md ``` Runs with `--output output/pending.md`. ## Prerequisites ### When Using Synced Data (Recommended) Emails must be synced to `output/gmail/{account_name}/`. ``` output/gmail/ ├── my-account/ │ ├── 2026-01-27/ │ │ ├── index.md # Daily index │ │ ├── 19bfd03adcbf0235.md # Individual email │ │ └── ... │ └── ... └── work/ └── ... ``` Format of each email file: ```yaml --- id: 19bfd03adcbf0235 subject: Subject from: Sender <email@example.com> date: 2026-01-27 10:13:51 attachments: file1.pdf, file2.xlsx # Optional --- # Subject Email body... ``` ### When Using API (Optional) The `GMAIL_ACCOUNTS_CONFIG` environment variable must be set with multi-account configuration: ```json { "accounts": [ { "label": "work", "type": "service_account", "subject": "user@company.com" }, { "label": "personal", "type": "oauth", "client_id_env": "GMAIL_PERSONAL_CLIENT_ID", "client_secret_env": "GMAIL_PERSONAL_CLIENT_SECRET", "refresh_token_env": "GMAIL_PERSONAL_REFRESH_TOKEN" } ] } ``` ## Output Format ### 1. Unreplied Email List ``` Emails requiring a reply (default): 2 items Target period: Past 7 days ====================================================================== 1. About the project progress report - Action required Date: 2026-01-27 10:13 From: Taro Yamada <taro.yamada@example.com> Type: Request/Task Summary: Report review request Link: https://mail.google.com/mail/u/0/#inbox/xxx 2. About the monthly meeting agenda Date: 2026-01-23 13:53 From: Hanako Sato <hanako.sato@example.com> Type: Information sharing (CC) Summary: Agenda draft sharing Link: https://mail.google.com/mail/u/0/#inbox/yyy ====================================================================== ``` ### 2. Auto-Generated Reply Drafts (for request/question emails only) Reply drafts are automatically generated for emails containing requests or questions: ``` --- ## Reply Draft: About the project progress report Subject: Re: About the project progress report Dear Mr. Yamada, Thank you for reaching out. I acknowledge your request for the report. I'm planning to prepare the report in the following categories: [1. Information gathering/search] - Cross-search and summary generation for Slack/Gmail/Calendar [2. Document/material creation] - Automatic generation of workflow diagrams [3. Formatting/transcription] - Data cleansing and format conversion I will send the materials by the end of this week. --- ``` ## Exclusion Patterns The following emails are automatically excluded: | Category | Example Patterns | |----------|-----------------| | Notifications | noreply, no-reply, notification | | Banks | @bank.gmo-aozora.com | | Events | @peatix.com, @morningpitch.com | | Auto-sent | spamdigest, Moderator | | Meeting invitations | .ics attachments, teams.microsoft.com | ## Related Commands - `/extract-tasks` - Task extraction from multiple sources (includes Gmail) - `/slack-pending-replies` - Slack version of unreplied message extraction

{ "prompt": "# Gmail Pending Replies - Extract Unreplied Emails\n\nExtract emails that need a reply from Gmail and **automatically generate reply drafts**.\n\n## Target Categories\n\n1. **Unreplied emails**: Emails addressed to you (TO/CC) that you haven't replied to\n2. **Thread replies**: Threads you started where the last reply is from someone else\n\n## Data Sources\n\n### Method 1: Use Synced Data (Recommended)\n\nAnalyze Markdown files synced to `output/gmail/{account_name}/`.\n\n| Account | Path | Your Address |\n|---------|------|-------------|\n| default | `output/gmail/default/` | `user@example.com` |\n| work | `output/gmail/work/` | Corresponding address |\n\n### Method 2: Via API (When GMAIL_ACCOUNTS_CONFIG Is Set)\n\n```bash\npython src/get_gmail_pending_replies.py --days {days}\n```\n\n## Steps\n\n### Step 1: Extract Parameters\n\nExtract the following from the user's input:\n- **Days**: Number of target days (default: 7)\n- **Account**: Specific account only (default: all)\n- **Output format**: markdown / json (default: screen display)\n\n### Step 2: Scan Emails\n\nAnalyze synced data at `output/gmail/{account}/YYYY-MM-DD/*.md` and extract:\n- Received emails from people other than yourself\n- Exclude notification emails (noreply, bank, peatix, etc.)\n- Exclude meeting invitations (.ics attachments)\n- Exclude emails with the same subject where you've already replied\n\n### Step 3: Display Results + Auto-Generate Reply Drafts\n\n1. Display the list of unreplied emails\n2. **Analyze the content of each email and determine its type**:\n - **Request/Task**: Something requiring a specific action\n - **Question**: Something requiring an answer\n - **Information sharing**: No reply needed (shared via CC, etc.)\n\n3. **Automatically generate reply drafts for request and question emails**:\n - Read the email body\n - Reference related project information if available\n - Create an appropriate reply draft\n\n## Options\n\n| Option | Description | Default |\n|--------|-------------|---------|\n| `--days INT` / `-d` | Number of target days | 7 |\n| `--account TEXT` / `-a` | Specific account only (label name) | all |\n| `--output PATH` / `-o` | Output file path (.json / .md) | stdout |\n\n## Usage Examples\n\n### Basic execution\n\n```\n/gmail-pending-replies\n```\n\nRuns with default settings (7 days, all accounts).\n\n### Specify number of days\n\n```\n/gmail-pending-replies 3 days\n```\n\nRuns with `--days 3`.\n\n### Specific account only\n\n```\n/gmail-pending-replies personal account only\n```\n\nRuns with `--account personal`.\n\n### Save as Markdown\n\n```\n/gmail-pending-replies save to output/pending.md\n```\n\nRuns with `--output output/pending.md`.\n\n## Prerequisites\n\n### When Using Synced Data (Recommended)\n\nEmails must be synced to `output/gmail/{account_name}/`.\n\n```\noutput/gmail/\n├── my-account/\n│ ├── 2026-01-27/\n│ │ ├── index.md # Daily index\n│ │ ├── 19bfd03adcbf0235.md # Individual email\n│ │ └── ...\n│ └── ...\n└── work/\n └── ...\n```\n\nFormat of each email file:\n```yaml\n---\nid: 19bfd03adcbf0235\nsubject: Subject\nfrom: Sender <email@example.com>\ndate: 2026-01-27 10:13:51\nattachments: file1.pdf, file2.xlsx # Optional\n---\n\n# Subject\n\nEmail body...\n```\n\n### When Using API (Optional)\n\nThe `GMAIL_ACCOUNTS_CONFIG` environment variable must be set with multi-account configuration:\n\n```json\n{\n \"accounts\": [\n {\n \"label\": \"work\",\n \"type\": \"service_account\",\n \"subject\": \"user@company.com\"\n },\n {\n \"label\": \"personal\",\n \"type\": \"oauth\",\n \"client_id_env\": \"GMAIL_PERSONAL_CLIENT_ID\",\n \"client_secret_env\": \"GMAIL_PERSONAL_CLIENT_SECRET\",\n \"refresh_token_env\": \"GMAIL_PERSONAL_REFRESH_TOKEN\"\n }\n ]\n}\n```\n\n## Output Format\n\n### 1. Unreplied Email List\n\n```\nEmails requiring a reply (default): 2 items\nTarget period: Past 7 days\n\n======================================================================\n\n1. About the project progress report - Action required\n Date: 2026-01-27 10:13\n From: Taro Yamada <taro.yamada@example.com>\n Type: Request/Task\n Summary: Report review request\n Link: https://mail.google.com/mail/u/0/#inbox/xxx\n\n2. About the monthly meeting agenda\n Date: 2026-01-23 13:53\n From: Hanako Sato <hanako.sato@example.com>\n Type: Information sharing (CC)\n Summary: Agenda draft sharing\n Link: https://mail.google.com/mail/u/0/#inbox/yyy\n\n======================================================================\n```\n\n### 2. Auto-Generated Reply Drafts (for request/question emails only)\n\nReply drafts are automatically generated for emails containing requests or questions:\n\n```\n---\n## Reply Draft: About the project progress report\n\nSubject: Re: About the project progress report\n\nDear Mr. Yamada,\n\nThank you for reaching out.\nI acknowledge your request for the report.\n\nI'm planning to prepare the report in the following categories:\n\n[1. Information gathering/search]\n- Cross-search and summary generation for Slack/Gmail/Calendar\n\n[2. Document/material creation]\n- Automatic generation of workflow diagrams\n\n[3. Formatting/transcription]\n- Data cleansing and format conversion\n\nI will send the materials by the end of this week.\n---\n```\n\n## Exclusion Patterns\n\nThe following emails are automatically excluded:\n\n| Category | Example Patterns |\n|----------|-----------------|\n| Notifications | noreply, no-reply, notification |\n| Banks | @bank.gmo-aozora.com |\n| Events | @peatix.com, @morningpitch.com |\n| Auto-sent | spamdigest, Moderator |\n| Meeting invitations | .ics attachments, teams.microsoft.com |\n\n## Related Commands\n\n- `/extract-tasks` - Task extraction from multiple sources (includes Gmail)\n- `/slack-pending-replies` - Slack version of unreplied message extraction", "variables": [], "notes": "Extract emails that need a reply from Gmail and **automatically generate reply drafts**.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/minicoohei/ai-agent-camp", "path": ".cursor/commands/utility/gmail-pending-replies.en.md", "ref": "66ceb848c302e1f1831ed0f4ecb428fd6df44cfd", "url": "https://github.com/minicoohei/ai-agent-camp/blob/66ceb848c302e1f1831ed0f4ecb428fd6df44cfd/.cursor/commands/utility/gmail-pending-replies.en.md", "key": "minicoohei/ai-agent-camp/.cursor/commands/utility/gmail-pending-replies.en.md" } } }

gmail-pending-replies.en

About